> On Friday 24 January 2003 10:55 am, Beman Dawes wrote:
> > I don't know if that is the right mechanism, but it revision dates are at
> > least desired if not required in a lot of projects, so some kind of
> > solution is needed.
>
> It looks like CVS might help. The keyword $Date$ is expanded to contain the
> checkin date/time. We might just require that each document have, at the
> beginning,
> <last-modified>$Date$</last-modified>
The only problem is that the it will come polluted with the
some header stuff like:
<last-modified>$Date: 2003/01/26 00:00:00 $</last-modified>
I notice in one of the docbook examples they use:
<releaseinfo role="meta">
$Id: titlepage.xsl,v 1.4 2003/01/20 21:44:26 nwalsh Exp $
</releaseinfo>
They also use this in a comment:
<!-- ********************************************************************
$Id: titlepage.xsl,v 1.4 2003/01/20 21:44:26 nwalsh Exp $
******************************************************************** -->
to keep all the CVS meta-data. Either way, the file would have a clear
tracking back to the repository version info.
> We can then find the <last-modified> element nearest a particular element to
> figure out when it was last modified. Anyone want to look into this?
What did you want someone to look into? Just change one of your CVS
file to include the special syntax and check it into CVS. The info
is updated automatically...
Jeff
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
