As the FAQ mentions, I'd use my build script to do this. For instance,
if you're using Ant/Nant, you can append the svn log to the file (with
appropriate comments as needed). A more complicated solution would be to
still use the $Log$ in your files and have the build script search for
and replace it with the svn log.
From what I've seen in the way of using $Log$, you only need to use it
on official releases or exports. Build scripts should be able to solve
this pretty easily. That would nullify the out-of-sync log message
problem mentioned in the FAQ.
If you aren't using a build system, consider using one (even if you're
not compiling files). Build systems can save a lot of time in arranging
files and packaging deliverables. I use them a lot for small, tedious
tasks that I have to do a lot. Oh, and if you do look at them, just know
that Nant is more powerful than Ant (unless you include the compiling
Java part :-P). Just my humble opinion.
Michael Flanakin
-----Original Message-----
From: Arnette, Bill [mailto:billa@signalscape.com]
Sent: Friday, September 16, 2005 9:11 AM
To: users@subversion.tigris.org
Subject: $Log$ keyword alternatives
I understand the reasoning behind this:
http://subversion.tigris.org/faq.html#log-in-source
I am just curious what others are doing instead? Manual update of the
changelog in the file?
Thanks,
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 16 16:28:57 2005