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

Commit Log File

From: Jonathan Smith <jonsmith_at_members.limitless.org>
Date: 2003-05-13 16:35:37 CEST

I am looking at replacing our current CM toolset with subversion. The
only issue I have left in the 'can it be done' category is the following:

We keep a logfile for th our project, keeping all commit messages in one
place. The format is not of high priority, but the content is. The data
is as follows:

Commit Number (keyword LastChangedRevision)
Commit Developer (keyword LastChangedBy)
Commit Date (keyword LastChangedDate)
Commit Message (user specified)
Change Type (user specified)

Now, except for the commit number, all of this is known before the commit
and can be manually entered into the file (this would be acceptable and is
the current method). However, the Commit Number, as generated by svn, is
not. Further, it could change as a result of other commits, so prediction
would be hard.

The general format of the file is as follows:

Header Lines
New Message
Old Messages

Using normal keyword substitution, the prevsiou line would need to be
altered with each new one. A sample solution would be to define a line
(or more of keywords) that get copied (like a template) then written out
substituted. So the user could just fill in extra data, commit and the
line would remain with the evaluated line beneath it.

Any ideas towards having this log file would be appreciated.


Jonathan Smith

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 13 16:33:47 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.