Re: problem with keywords in XML files

[Paul Sander]

On Oct 21, 2005, at 7:23 PM, Jim Hyslop wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Julian Opificius wrote:
> > Works fine thanks - with ": " after "Log", of course.
>
> Not necessary. CVS will insert the colon.
>
> Actually, Log is one keyword that really is more trouble than it's
> worth, for several reasons. First, it's easy to modify the text in the
> file, but not update the actual CVS log message. Second, it's murder
> trying to keep it straight when merging from branches.
>
> The other keywords can be useful, though. I'm not familiar enough with
> XML to second-guess what Paul's getting at, though.

My arguments are the classics regarding keyword expansion in any text 
file:

Merging branches is generally a pain when keywords are expanded; they 
introduce conflicts in those cases where the merge would otherwise 
complete automatically.

The keywords lose their significance when copied from one RCS- (or 
CVS-) based repository to another and the original settings are lost 
upon import or commit.  $Log$ also tends to list multiple different 
entries where the version spaces overlap in the two repositories.

The historical record resulting from repeated expansions of the $Log$ 
keyword can be inaccurate or misleading if someone edits it.

--
Paul Sander       | "When a true genius appears in the world, you may
address@hidden | know him by this sign:  that all the dunces are in
                  | confederacy against him."  -- Jonathan Swift, 
writer.