Re: [PATCH] -R shortcut for --recursive

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> What commands are you invoking so often that "--recursive" becomes
> common for you?

Depending on your definition of "often", maybe nothing. The command
i'm always using --recursive with is revert. I don't use it as
often as up, or ci, but i use it often enough for it to bother me.

> Just trying to gather some data here. We did only a long opt for
> recursiveness, because we expected it to be infrequently used. If
> that's turning out not to be the case, then this assumption needs to
> be revised.

> if a short opt is needed.) But would like to know what commands a
> "dry-run" mode is useful for -- the classic CVS use case is "cvs -n
> update", and we've already got that covered with "svn st -u".

   cleanup
   merge
   resolve (maybe? haven't used this command yet)
   revert
   switch

As for update, i agree with what someone else suggested on the
list, that update -n behave like cvs's did. Sure status -u already
has that covered, but maybe you can just reuse that code. If a
person wants to see what svn update does, it's logical to think of
update -n, not status -u. Sure, status -u will be documented, but
if it doesn't interfere with anything else, it seems like a good
idea to match expectations.

Of course, if you disagree with my assumption that people might
expect it, my reasoning isn't useful.

--
Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 05:58:27 2002