[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit log messages: Best practices?

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-05-04 03:15:50 CEST

On May 3, 2005, at 8:20 PM, Ben Jackson wrote:

> Hi all,
> I was wondering if anyone has any tips for best practices in
> composing commit messages. Should we require that authors note
> their name with commits, or is that a job for svnlook? How specific
> should you be about file paths, adds, removes, etc? I thought about
> something like the following:
> svn ci -m "[joeblow] Added project2/ to /svn/projects"
> svn ci -m "[janeblow] Updated menu functionality in /svn/projects/
> project1/menu.js"
> svn ci -m "[johnblow] First version of template complete in /svn/
> projects/project1"

I think it just clutters the commit message with redundant
information. Subversion already records the user that does the
commit and the files that were changed/added/copied, etc.

look at the output of

svn log -v


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 4 03:17:27 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.