bob@proulx.com (Bob Proulx) writes:
> The subversion project HACKING file very nicely documents how to keep
> the svn log history in a useful change log format. If you have not
> read I highly recomend it. Additionally some coding standards (such
> as GNU) require an actual ChangeLog file to be included in source
> distributions. This means that generally similar information is
> available in two different places. Certainly with RCS/CVS a ChangeLog
> is really useful. But Subversion offers changesets and a unified log
> history of the project.
>
> I am curious
>
> a) if people are actively keeping a ChangeLog file so that it is
> available offline and in distributions?
>
> b) if people are using the svn log as the only change log?
>
> c) if people don't bother to maintain a project log?
>
> Depending on the project I have been continuing a) with a ChangeLog
> file in addition to the svn log. In others I do b) only making use of
> the svn log by itself. To me c) is anathema.
>
> I am debating with myself the merits of each and trying to decide what
> to do about future projects and am looking for input from the group.
> Do you still keep a separate ChangeLog?
We do (b) in the Subversion project. See the function 'quicklog' in
http://svn.red-bean.com/repos/kfogel/trunk/.bashrc, and its callers,
for some helper code. See also http://freshmeat.net/projects/svn2cl/.
-Karl
--
www.collab.net <> CollabNet | Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 10 23:16:43 2006