Re: --dry-run

Ben Collins-Sussman <sussman@collab.net> writes:
> 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.

Right. Could svn --dry-run commit print the same output?

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

Exactly. could svn --dry-run update print out the exact same thing
here, too?

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

Yes, but the documentation is a bit confusing to users on this.

Anyway, this is a "fit and finish" issue more than anything. I
realize the information is present with another command. The users are
just used to doing stuff like "cvs -n update", and having
"svn --dry-run update" do the same thing (i.e. print out what
svn status -u prints) would reduce retraining.

-- 
Perry E. Metzger		perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org