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

Re: [TSVN] Merge dialog, second attempt

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-01-24 20:14:44 CET

SteveKing <steveking@gmx.ch> wrote on 01/24/2005 02:07:17 PM:

> So since some people don't want the revisions to merge entered (no
> matter how it is dome) but the range specified the same way as the CL
> client I've created another merge dialog.
> To be honest, I've already committed that change. Even if it doesn't get

> your ok, it's better than what we have now and we can always improve it
> further if we ever get to an agreement on how it should look/work.
>
> So please comment on it. But don't get away with new features like
> remembering which revisions were already merged, ... - those are
> features Subversion will implement someday itself.

I agree it will be an improvement. Thanks.

In the text for "To:" you are missing the word "and" between URL and
revision.

I will respect your wish to not discuss remembering previous merges, but I
do not completely agree that this is what Subversion means by merge
tracking and that everything must wait until they implement it. That
being said, I do agree that the end results would be the same or similar.
In my view, that is all the more reason to implement something in the GUI
tools.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 24 20:15:23 2005

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

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