Karl Fogel wrote:
The real issue is that '-r COMMITTED' isn't really meaningful for
directories.
The real-life problem is to answer this question : What is the
last revision in which something under the foo/ directory has been modified.
(in other words, a branch-local HEAD) (I haven't tried svnversion yet.)
For files, it means show the logs for the base revision of that file
in your current working copy (that is, for the revision of the text
base, which may have resulted from an update or from a commit). This
is the same as the committed-rev in the .svn/entries file.
But directories have mixed revisions, so the COMMITTED rev is,
essentially, a set. It could be a very wide distribution of numbers,
depending on how much committing one has done under that tree without
updating from the top.
COMITTED doesn't require network access, does it ?
Frankly, I think we should either error when it is used with a
directory, or treat it like HEAD. Thoughts?
But HEAD requires network access. I don't think that requiring that
COMMITTED on dirs has network access is consistent. Moreoever,
treating it like HEAD may confuse users. So, forbidding it on
directories is fine with me.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:03:10 2006