<quote who="Kevin Brosius"> >> technically cvs does this for us :) > > Well, that was partially my point. But now that I think about it: > > - No, cvs only tracks who changes what. We need to encourage commit > comments that say what the change does functionally. > - I'd suggest not using the ChangeLog files on pre 1.0 apps/libs and > sticking to it. For packages that are stable, then a ChangeLog should > be maintained. Does anything in the e17 tree fall in that category > yet? Maybe efsd, you might say evas, entice, ...? That's a small > percentage.
Eh..... being BSD we aren't required to maintain strict Changelog's so it's not really a sorry, but I still think that CVS handles this problem fine.Whenever you commit your adding a description of what you changed. The CVS web interface reflects this on a per-file basis, including annoted code of that change. It's entirely supperior to a standard Changelog. This assumes that you actually do make useful comments about what you change. Obviously commits with a description of "a commit" isn't helpful....... and the only times we see commits with lame descriptions is when they are fixes to previous well explained commits. benr. -- //Ben Rockwood - UNIX Systems Admin //email: [EMAIL PROTECTED] //web: www.cuddletech.com //-> We do what we can, We give what we have, //-> Our doubt is our passion, and our passion is our task, //-> The rest is the madness of Art. //-> -Henry James ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
