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

Re: Version change rationale.

From: Jeff Smith <jsmith_at_robotronics.com>
Date: 2007-01-10 18:31:01 CET

On Tuesday 09 January 2007 23:46, Owen Thomas wrote:
> I would like to be able to record why changes were made to a
> revision in a separate file to the one subject to the revision. I
> would like to keep this revision file under version control as
> well.

I've wanted to do it too...

As Eric pointed out, the svn log is a necessity, not a non-standard
location for notes. Also I notice there would be no problem with
adding a file which has detailed documentation of your projects. I
don't see what feature you are missing in order to simply add that
document to the repository as you wish.

1. Keeping most revision notes in the svn log is important because it
will be automatically associated with other attributes of said

2. You can use a file in the working folder as a source of the text
submitted to svn log. If it's too complex to say `svn commit -m
"explanation of what was changed" `, you can say

$ svn commit --force-log --file file_under_vc.txt foo.c

where "file_under_vc.txt" is that file where you write changes. If
that file is under version control, you also need the "--force-log".
This wouldn't be practical though if you insist on keeping a file
with all history (as apposed to overwriting with only latest
changes), because every log entry would have also previous log
entries... making a mess.

See 'commit' in the svn-book.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 10 18:31:39 2007

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.