Re: COMMITTED and subdir recursion

Benjamin Pflugmann benjamin-svn-dev@pflugmann.de writes:
 Given that using COMMITTED makes only sense with network access, why
 don't query the server for that info? I do not think that it makes
 much sense to have a COMMITTED that is fetched from a place that can
 be out of date (I realize that this only affects dirs, but my point
 stands anyhow).

The real issue is that '-r COMMITTED' isn't really meaningful for
directories.

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.

Frankly, I think we should either error when it is used with a
directory, or treat it like HEAD. Thoughts?

-K

---------------------------------------------------------------------
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:04 2006