Re: Suggestions for replacement of legacy revision documentation

I'll further that: if it's meant to be human readable, why not format
it into HTML?

The colors are nice when viewing in Emacs, but are there any good
reasons for keeping this in ChangeLog format?


Phillip Lord writes:
 > 
 > 
 > Paul Landes <[email protected]> writes:
 > > Great suggestions.  I think the way to go is a hybrid.  That is, keep
 > > the old ChnageLog and add to it using the `svn log --xml' by using an
 > > XSL transform.
 > >
 > > I actually looked at the tool and I think a simpler/easier way to go
 > > is to use the XSLT functionality in Ant and use the XSL transform
 > > document the tool supplies, which is at:
 > >
 > >   http://svn.collab.net/repos/svn/trunk/contrib/client-side/svn2cl/svn2cl.xsl
 > >
 > > The only hang up I have is that the output it generates is slightly
 > > different from the ChangeLog that already exists, and the formatted
 > > change-log-mode likes.  Here's an example of the output of the XSL
 > > transform:
 > 
 > If it's meant to be human readable, then I wouldn't worry about this.
 > Even if someone had built computational tools over the change log, it
 > would be easier to rewrite them to just use the XML from SVN. 
 > 
 > However, I suspect, that the ChangeLog is not the same as the VC
 > history. It's there to give a precis of the changes, not all the
 > details. 
 > 
 > Phil
 > 
 > 


-- 
Paul Landes
[email protected]

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july