Re: Possible way to support $Log$

John Peacock <jpeacock@rowman.com> writes:

> I was thinking the other day about $Log$, which some people have complained
> about missing. AFAIK, there are three things that prevent $Log$ from being
> easily supported in Subversion:
>
> 1) All keyword processing (expansion) is line oriented (i.e. both $ delimiters
> must be on a single line;
>
> 2) The contents of $Log$ cannot include the $ delimeter;
>
> 3) Causes difficulties with merging (this is from CVS' experience).

There is also the question of whether $Log$ should expand to the log
for the entire repository or to the log for the file containing the
keyword; I haven't really followed the discussion but seen some people
appear to want one, and some people the other.

I think CVS's $Log$ is the log for the file (I'm not a CVS user) and
there isn't really a direct equivalent for that in Subversion, there
is only the log for the atomic commits that included the file in
question.

A further complication is that however $Log$ is expanded the log
messages can be changed, so the client is going to have to download
the log message on every update. That looks like a real performance
killer.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org