Re: Proposal for $Revision$ keyword amendment

On 9/29/05, Molle Bestefich <molle.bestefich@gmail.com> wrote:
> One of the reasons being that since it's entirely (easily?) possible
> to implement a keyword which reflects 'working copy last commit' in
> Subversion, it's dumb that every developer or admin or whatever around
> the world has to waste his time implementing his own inferior solution
> in his own build scripts (or what not).

Assuming you were right and it was easy to implement, but it inflicts
great inefficiency - every file in your project would suddenly have to
be scanned for any update.

In reality, a repository-wide checkout number is filled with
ambiguity, because a working copy can have different files and
directories based at different points in time (a mixed wc). if src/foo
was checked out with -r 100 and src/bar was checked out with -r 200,
what is this 'checkout revision' supposed to correspond to?

-David Waite

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 29 22:42:57 2005