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

Re: Ok. I just had this brainstorm....

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-09-25 05:36:19 CEST

"Files" <files@poetryunlimited.com> writes:

> Ok.
>
> Do we have some way of entering a template for the log message?

No.

>
> So that when we get in there, instead of a line that says "------
> everything below this line will be ignored---------", we can have
> those files already listed as part of the log and we can add our
> comments to them?

The one 'template' that comes up already has the modified files
listed. Just remove the "------ XXXX -----" line, and you can make
whatever comments you want. Or leave the divider in, and write your
own message based on the file list.

> Or a switch perhaps that would make the files part of the default message?
>

I don't understand... the files *are* in the default message already.

> I am wondering because it seems to me that when we are making
> changes, we spend a lot of time entering the log message or we
> forget to include something.
>
> How do you all do it? Do you maintain a list of changes externally
> and then just read that file into the log editor?

Many of us write the log message as we code. For example, when I
change a function, I hit "C-c, l" in emacs, and it instantly switches
me to a logmsg buffer in-progress, and inserts a line like:

  * filename.c (function):

So I can instantly document what I just changed. By the time I'm
ready to commit, I just run 'svn commit -F logmsg'.

Other people write the log message all at once, just before they
commit. Typically they run 'svn status' and 'svn diff', read
carefully, and document every changed function. They commit with the
-F switch as well.

Or, in the simplest case, don't give any args to 'svn commit', and the
default $EDITOR will pop up a list of changed files, ready for you to
document. When the list is in front of you, I don't quite understand
how you can forget to document something...?

 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 05:37:50 2003

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

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