[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: Michael W Thelen <thelenm_at_cs.utah.edu>
Date: 2004-04-13 23:33:20 CEST

* Perry E. Metzger <perry@piermont.com> [2004-04-13 13:27]:
> 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.

Being a CVS user and fairly new to SVN myself, I would say it took me maybe a
few hours to get used to 'svn status' and 'svn status -u'. If these commands
do exactly what your users are looking for, why can't your users also make a
habit of using them? There is a little brain strain at first, but once you
get used to it 'svn status' and 'svn status -u' work just fine (and are more
intuitive than their CVS counterparts, I'd say).

-- Mike

Michael W. Thelen
No amount of genius can overcome a preoccupation with detail.
                -- Levy's Eighth Law

  • application/pgp-signature attachment: stored
Received on Tue Apr 13 23:36:50 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.