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

Re: --dry-run

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-04-13 21:16:14 CEST

On Tue, 2004-04-13 at 14:11, Perry E. Metzger wrote:
> One of my users, who's an old CVS hand, notes that the fact that
> svn --dry-run doesn't provide them with information when they're doing
> commits or updates bothers them. I have told them to use
> svn status --verbose for now, but would it be difficult to get fairly
> similar information printed out when update or commit were run with
> --dry-run? That's apparently pretty much what cvs -n used to do for them...

I'm not sure what you're asking here, probably because I'm not much of a
cvs user, and don't know cvs switches.

If you want to see what 'svn commit' *would* commit, without actually
committing, just run 'svn status'. You get instant list of
modified/scheduled things.

If youw want to see what 'svn up' *would* modify, without actually
updating, run 'svn status -u'. It's the same as 'svn status', except
that it contacts the server and adds little asterisk marks next to every
file which is out-of-date. If you see a "*" and "M" on the same file,
it means you're in for either a merge or a conflict.

(FWIW, the --dry-run flag only exists for 'svn merge'.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 13 21:18:17 2004

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

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