Hi guys,
Can someone help me step by step on how to upload a patch to the bugtracker?

It?s a small patch with a bugfix and i like to start contributing but i m not familiar with community tools yet

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140408/e6f37f63/attachment.html> -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1046 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140408/e6f37f63/attachment.png>

Basically, make a new issue in the bugtracker and attach the patch against Laz trunk (or FPC trunk, depending, of course) using Upload File in the bug screen.

More info:
http://wiki.lazarus.freepascal.org/How_do_I_create_a_bug_report http://wiki.lazarus.freepascal.org/Tips_on_writing_bug_reports http://wiki.lazarus.freepascal.org/Creating_A_Patch http://wiki.lazarus.freepascal.org/Database_bug_reporting

Creating the patch is my main consern...
i m getting the trunc version now and i ll try tortoisesvn's way

ps: is it bad that i prefer to use the stable version? trunc is so scary sometimes... :P

-----?????? ??????-----

Chris Crori wrote

Creating the patch is my main consern... i m getting the trunc version now and i ll try tortoisesvn's way

Ok. Please feel free to post if you hit problems.
I'd suggest including the command line tools with your tortoisesvn install so that you can run svn.exe on the command line as well... gives you more choices.

ps: is it bad that i prefer to use the stable version? trunc is so scary sometimes... :P

Well, Laz trunk has been generally quite stable for me on Win x86... And as you can have multiple versions of Lazarus (and FPC) installed side by side, you can choose what you work on...

Chris Crori wrote

Creating the patch is my main consern... i m getting the trunc version now and i ll try tortoisesvn's way

Ok. Please feel free to post if you hit problems.
I'd suggest including the command line tools with your tortoisesvn install so that you can run svn.exe on the command line as well... gives you more choices.

ps: is it bad that i prefer to use the stable version? trunc is so scary sometimes... :P

Well, Laz trunk has been generally quite stable for me on Win x86... And as you can have multiple versions of Lazarus (and FPC) installed side by side, you can choose what you work on...

Sometimes i prefer babysteps, just so i am perfectly aware of what i am doing :)
I think i made a mistake and the bug was assigned to someone... i just hope the path finds it way to the version!
btw i never realized that FPC was not on Lazarus trunk before!!!

Chris Crori wrote

On 08/04/2014 13:24, Chris Crori wrote: I think i made a mistake and the bug was assigned to someone...

You mean bug 25987? No - as it's an FPC database bug it gets automatically assigned to Joost van der Sluis (addmittedly this shows up a bit weird in the history); I then assigned that to myself in order to deal with it.

i just hope the path finds it way to the version!

As I explained in that bug report, the issue has already been fixed in trunk. As you can see in the linked/original bug report, I've set the target version for that fix to FPC 2.8.0 so the devs can keep track of what needs to be backported (if that is possible) if there is a 2.8 release.

btw i never realized that FPC was not on Lazarus trunk before!!!

FPC and Lazarus are different projects. Both have stable and trunk versions. You can compile trunk Lazarus with stable FPC, trunk Lazarus with trunk FPC etc.

(It would also be more appropriate to post on the FPC list instead of Lazarus when talking about FPC patches/bugs)

PS: Chris, could you please properly quote messages? Helps keep track of who said what... Thanks.

Oops, sorry, backported to 2.8 is not the correct term. Currently we're on fpc trunk having 2.7.1 and 2.8 would be the release based on that code.

Chris Crori wrote

On 08/04/2014 13:24, Chris Crori wrote: I think i made a mistake and the bug was assigned to someone...

You mean bug 25987? No - as it's an FPC database bug it gets automatically assigned to Joost van der Sluis (addmittedly this shows up a bit weird in the history); I then assigned that to myself in order to deal with it.

- :) great!

i just hope the path finds it way to the version!

As I explained in that bug report, the issue has already been fixed in trunk. As you can see in the linked/original bug report, I've set the target version for that fix to FPC 2.8.0 so the devs can keep track of what needs to be backported (if that is possible) if there is a 2.8 release.

- I considered about the same fix, and later for the reasons i explained in the bug report i prefer my way

btw i never realized that FPC was not on Lazarus trunk before!!!

FPC and Lazarus are different projects. Both have stable and trunk versions. You can compile trunk Lazarus with stable FPC, trunk Lazarus with trunk FPC etc.

(It would also be more appropriate to post on the FPC list instead of Lazarus when talking about FPC patches/bugs)

- I am figuring out one thing at a time, i may need some patience :)

PS: Chris, could you please properly quote messages? Helps keep track of who said what... Thanks.

- I will do... for now, it's like these preferences are hidden! (promise next time to have it fixed)

Thank you Reinier for everything