Re: The hated $Log$ keyword

[James Youngman]

Richard Wesley <address@hidden> writes:

> BTW, I appreciate the arguments against using $Log$ (redundancy, 
> merging, admin -m, etc.), but these guys really like the Header 
> Comments functionality they had with another system (MPW Projector) 
> so I'm trying to figure out what will work best for everyone.  At 
> least they aren't bitching about concurrency ;-)


I also get bitten by $Log$ when merging, but OTOH I still use it.
This is partly because some of the projects I work on use "cvs export"
to affiliated projects whose only access to log information is
readeing the expanded log (though, yes, ChangeLog would be as good for
this).   

What if there was a keyword like $Log$ but which expanded to the
entire log history (with comment leaders)?   This would avoid the
merge problem and surely cannot be too expensive to compute.
Thoughts?

-- 
James Youngman
Manchester, UK.  +44 161 226 7339
PGP (GPG) key ID for <address@hidden> is 64A95EE5 (F1B83152).