"Diethelm Guallar, Gonzalo" wrote:
>
> Ok, I'm willing to do it the way the group decides.
> Before that, one suggestion to Jon: it is VERY
> helpful to have a ChangeLog file, with comments
> for all commits. This is usual in most Open Source
> projects I have seen. This way, the ChangeLog file
> has entries like:
>
> 2000-0820 12:44:36 [EMAIL PROTECTED]
>
> * src/java/org/apache/turbine/foo.java
> * src/java/org/apache/turbine/bar.java
> Now foo and bar do The Right Thing (TM).
>
> and the commit is issued like this (one liner):
>
> cvs commit -m"ChangeLogTag: 2000-0820 12:44:36 [EMAIL PROTECTED]"
> turbine
>
> This way, you can always check what files where committed as
> a whole. There is even a key in emacs (C-x 4 a) that will look up
> the proper ChangeLog file for the file you are editing, and insert
> the commit entry automatically.
>
> This is just a suggestion, that I have seen produce good results.
> If the wisdom of the group is to comment changes on the
> commit message, I'll follow it.
It's easier on the programmers to have the CVS *server* do the ChangeLog
generation. Karl Fogel has this setup for the Subversion project, so we
could steal it from him.
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
