[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: Daniel L. Rall <dlr_at_finemaltcoding.com>
Date: 2005-08-04 17:56:51 CEST

On Thu, 2005-08-04 at 17:39 +0200, Marc Haisenko wrote:
> On Thursday 04 August 2005 17:09, Řyvind A. Holm wrote:
> > On 2005-08-04 10:59:49 Mark Phippard wrote:
> > > cmpilato@localhost.localdomain wrote on 08/04/2005 10:51:10 AM:
> > > How about a new "cherry-pick" syntax like: --revs 14,17,21 that would
> > > merge those specific revisions?
> >
> > Ooooo.... NICE! Yes, one of those, please. And maybe it could be
> > extended to "-r14,17,21:29,35" ?
> >
> > Cheers,
> > Řyvind A. Holm
> Just some user feedback...
> How often have you wished you could do something like that ? O_o I don't see
> any real-world value here, at least I am very careful when merging stuff and
> rather do it step by step and would never ever do something like this... but
> of course I can see the geek value here ;-)

I need to do this quite often when working with multiple branches (a
state which I continually find myself in). In fact, just yesterday I
left a change sitting in the 1.2.x branch's STATUS file rather than
merging it because it consisted of so many revisions:

  * r14008, r14458, r14587, r14632, r15329, r15340
    Fixes to svnmerge.
      It would be good to have contrib code be the latest and fixed
      version. We don't guarantee that this code works, but it would
      be good to have known fixes released. This fixes four issues.
      Blair has used the code in trunk in a production environment and
      it works great.

Being able to practically cut and pate that first line to my
command-line client would've been a significant speed-up, and an overall
usability plus.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 4 18:01:27 2005

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

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