[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:29:59 CEST

Nuutti Kotivuori <naked@iki.fi> writes:
> The single piece of information that I quite often wish to obtain is
> that "Are there any newer revisions in the repository than my current
> working copy?" If the answer to that is yes, then I usually do want to
> atleast see what those new revisions were by checking the log
> messages, even though they might have not been relevant - and if they
> were relevant, I want to do an update at the top of the tree. And I
> want to do this checking just about anywhere in my working copy.

And also:
> 1) If there are no changes, you only see the "Head revision" - so I do
> not know if there are any new revisions in the repository.
> 2) It takes an awfully lot more CPU time and goes through files,
> compared to 'svn up' - or 'svn st -v README'.

There's no way to avoid (2) and get what you want, I think. In order
to know if the repository has newer things than your working copy, svn
has to know what's in your working copy.

Try "svn st -nu", maybe?

> Actually, I'm not so sure as to what I really want - maybe I need to
> go into that further before I do anything. If the above case is
> solved, then it's just a gut feeling that I want to be notified when
> something changes even in the svn internals in the working copy - as
> opposed to a real no-op which happens when there were no new
> revisions.

I don't know if there's a good solution here.

In general, svn probably can't provide a single command for every use
case. Most people just run "svn up" whenever they're wondering what's
happened lately, I guess (if they're not already watching commit

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:29:54 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.