standards for making log entries?

[Todd Eddy <vr...@neo.rr.com>]

Hi, been using svn for little projects here and there and so far so 
good.  One thing I've been wondering about it is the update log when 
I commit something.  Right now I just use something to the extent of 
"changed formating of main page a bit".  That doesn't seem all too 
constructive if I wanted to create a changlog later.  would it be 
better to do something like:

index.php
* changed formatting when in edit mode

Or there's this other way that I've seen before that differentiated 
between things like bug fixes, new additions, and something else, 
maybe tweaks?  so it would look something like:

index.php
+ added option to change password on main screen
- fixed bug that would send your information to microsoft
* Improved the format of the main page so it's easier to understand

or something like that.  Was curious if anyone else has any system to 
it (which I'd imagine so since some people use this in big companies 
and stuff) or just do like my first example of "changed some stuff on 
the main page" :)  thanks in advance for any input on this
-- 
Todd Eddy
vrillusions@neo.rr.com
www.vrillusions.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: standards for making log entries?

[Michael W Thelen <th...@cs.utah.edu>]

* Todd Eddy <vr...@neo.rr.com> [2004-06-27 23:59]:
> or something like that.  Was curious if anyone else has any system to 
> it (which I'd imagine so since some people use this in big companies 
> and stuff) or just do like my first example of "changed some stuff on 
> the main page" :)  thanks in advance for any input on this

As a matter of fact, the Subversion project itself has a log message
convention like this.  You can read about it in the "Writing log
messages" section of the HACKING document here:

http://svn.collab.net/repos/svn/trunk/HACKING

And you can see it in action by doing an "svn log" on the Subversion
repository itself, for example:

svn log -r10000:10010 http://svn.collab.net/repos/svn/

-- Mike

-- 
Michael W. Thelen
Never express yourself more clearly than you are able to think.
                -- Niels Bohr