Re: Proposal for $Revision$ keyword amendment

Greg Hudson wrote:
> svn up -r16640
> svn up build.conf
>
> This yields a committed-rev of 16646 and a revision of 16654 (or
> whatever the current head is when you run the second command).

So it does. ;-) That was a little contrived, but this flow is more
realistic:

   $ vi some/file.c
   $ svn ci -m 'commit message' some/file.c
   $ svn up some/other-file.c

and which will indeed lead to other-file.c having a differing revision
and committed-rev.

So, there would be two pieces to implementing this keyword:

a) Add the keyword itself (trivial, actually);
b) Cause the file containing said keyword to be expanded even though it
is otherwise unchanged.

As you pointed out, implementing b) would also also be the fix for the
$URL$ rewrite in issue #1975.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org