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

Re: 'svn merge -rX' UI annoyance.

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-08-04 17:03:07 CEST

Mark Phippard <MarkP@softlanding.com> writes:

> cmpilato@localhost.localdomain wrote on 08/04/2005 10:51:10 AM:
>
> > I'm constantly frustrated that passing -rX (instead of -rX:Y) as the
> > operative range for merge operations doesn't default to -rX:X-1
> > behavior. Like, I wanna say "cherry pick a merge of revision 14" and
> > I run 'svn merge -r14 ...' only to get bounced for not having
> > specified a full revision range.
> >
> > What would others think about relaxing the 'svn merge' UI such that
> > passing a single revision means, "merge that one revision"?
>
> I assume you meant does not default to -rX-1:X?

Oops! Yeah, you're right. Sorry. -rX-1:X.

> I agree that this would be a nice usability win for the command. It
> would be nice if this also worked: -rPREV:X and then we could say
> that -rX implied the former.

I thought about that, but PREV already has a meaning and it ain't that
one. I'd rather not tainted the definition of PREV.

> How about a new "cherry-pick" syntax like: --revs 14,17,21 that
> would merge those specific revisions?

Nah, now you've got two different ways to specify revisions, and I
think that would cause more confusion than it clears.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 4 17:07:26 2005

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