Global revision keyword - why it is impossible

The problem:

To accurately represent the state of the tree, as svnversion does, we must
not only know which revision the tree is at, but also whether it is
modified - otherwise, a plain revnum can mislead.

There is no feasible solution that can cause spontanteous update of a
keyword in one file when a distant file within the same set of working copy
dirs is changed.

If we (riskily) decide to live without a 'modified' flag:

Then the problem is still awkward - any "svn update" or "svn switch" must
update files which possibly lay *outside* the area of tree on which they are
acting.
This would represent a significant new subsystem of code just to support
this one keyword, to produce an end result which is still inferior to
svnversion.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 28 01:12:30 2004