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

Re: svn commit: rev 1895 - trunk/subversion/clients/cmdline trunk/subversion/tests/clients/cmdline/svntest

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-05-08 00:45:19 CEST

Nuutti Kotivuori <naked@iki.fi> writes:
> Well that works quite fast ofcourse - but that brings me back to the
> same problem - I only see the new revision, not the revision that my
> wc is currently at. That is assuming ofcourse nothing changed under
> the current working directory.

It's that last sentence I don't understand.

Do you mean local changes, the kind that would be committed if you ran
"svn ci"? Or do you mean the case where your working copy is a
mixture of various revisions, instead of all being at the same
revision as (say) the directory you're running "svn st" or "svn up"

The phrase "the revision that my wc is currently at" is meaningless,
except when your wc all happens to be at one revision, or reflect the
content of one revision -- but to determine that, the entire wc still
has to be crawled by the client.

> Well that is exactly what I do, in the end. And the only thing running
> 'svn up' is lacking right now, for me, is that it would give some sort
> of a clue that the revision number got bumped, even though there were
> no changes to the directory you ran 'svn up' in.

Yeah. I still don't see how it helps your stated goal to see whether
revision number got bumped or not, though...

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 8 00:45:10 2002

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.