>>>>> "Owen" == Owen Thomas <othomas@wcg.net.au> writes:
Owen> Hello. I would like to be able to record why changes were
Owen> made to a revision in a separate file to the one subject to
Owen> the revision. I would like to keep this revision file under
Owen> version control as well.
Owen> That is, if a change is made to a file under change
Owen> management, I would like to be able to keep a record of why
Owen> that change was made in a separate file. I’m managing a
Owen> collection of Java projects, and this serves two purposes:
Owen> for files that permit comments, it keeps them to a minimum,
Owen> and for files that do not permit comments, it allows me to
Owen> keep some idea of why a change was made. In either case,
Owen> this allows me the opportunity to include a comprehensive
Owen> rationale for changes that, say, might link back to program
Owen> specs, design documents or other sources of info.
Owen> I have a very rough idea of how this might be implemented.
Owen> I’m almost sure someone would have come up with something
Owen> like this before, and I’d like to know what is out there
Owen> before I plunge in to doing my own thing.
Owen> Suggestions accepted with compliments,
If I were you, I wouldn't keep these comments in a separate,
revision-controlled file. Instead, I'd keep them in the svn:log
property, as God intended. Then, if I really wanted them in a file,
I'd add something to my build script that created the file from the
svn:log properties of the relevant revisions. There's already a tool
that does this: it's called svn2cl. Along with the freely-available
xslt tool, it's all you need to automatically create such a file from
the svn:log properties.
--
Keaton, Chaplin, Garbo - let them now make room for Gromit.
A. O. Scott, in The New York Times
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 10 08:08:52 2007