Re: [GD-DEVEL] New commits
[email protected] (Pierre)
| Newsgroups | php.gd.devel |
|---|---|
| Message-ID | <[email protected]> |
Hell Lars, I saw your first commits this morning, welcome on board! On 10/11/06, Lars Hecking <[email protected]> wrote: > Pierre writes: > > See http://www.libgd.org/Support .Send a mail to > > [email protected] (gd-devel) to subscribe, then follow > > the instructions in the confirmation mail. Let me know if it works > > well, we can then use the devel list, easier to archive :) > > Right. Let's see whether this works :) > > I have added a ChangeLog file and got this message: > > cvs add: Re-adding file `ChangeLog' (in place of dead revision 1.5). > cvs add: use 'cvs commit' to add this file permanently > > Was that a bad idea? Was there a reason for removing it in the first place? I added all files of all past GD releases. One of them has a ChangeLog file. But it was not really a ChangeLog. To ease my work, I created a "ISSUES" file. Each change has an id which will match the issue Id in the tracker. Can you add your changes in there? If it is related to one entry, like fixing a fix, there is no need to create a new one. It is not used directly now, but the format of the commit msg should be: #123, description of the commit where 123 is the issue id. Once the issues tracker is online, it will provide patches for each issue using all relevant commits. The final goal is to get the release changelog generated by the tracker. By the way, if you like to remove the "configure" and related data from cvs and add an autogen.sh, please do, we have to do it anyway :) --Pierre