[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: COMMITTED and subdir recursion

From: <philip_at_codematters.co.uk>
Date: 2003-01-20 22:02:57 CET

Karl Fogel kfogel@newton.ch.collab.net writes:

 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).

COMMITTED is *not* the most recent committed revision on the server,
it is the last change at or before the BASE revision in the working
copy. What you see is a consequence of Subversions mixed revision
policy, the COMMITTED value is not out of date, it still has the
correct value given the base revision of the directory.

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


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

I think the current behaviour is correct.

Philip Martin
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:09 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.