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

Even more merge thoughts...

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: Tue, 29 Nov 2011 11:31:14 +0000

Hi all!

Now with svn 1.7.2 coming up this might not be the best timing to come dragging with some more merge thoughts. But hey, is there ever a good time? :-)

Here are a few points that have come up during this round of merges:

- The Merge dialog contains the helpful hint "To merge all revisions, leave the box empty.". I have to keep remind people that this is indeed the case, and there's no need to enter any revision numbers if it's not cherry picking that we are after.
Maybe it would be a good idea to add a checkbox that says something like "Merge all revisions", that is checked by default and hides/grays out the rest of the "Revision range to merge" controls. Unchecking this box would enable/show the controls again.
This would make it clear even for new users that SVN will by default help you with the merging and there is no need to do select anything explicitly if you don't want to.

- In the Merge dialog when the "Show log" button is clicked, the Log dialog that opens will list revisions as far back as it can. This is mostly not what you want. I would say that the usual case would be to show revisions that are younger than the branch. Doing this would prevent the additional clutter of showing lots of revisions that are already, implicitly, part of the branch.
I would suggest to add yet another checkbox to the log dialog that says "Stop on branch creation". This checkbox would _only_ be visible when the log dialog is opened from the Merge dialog. The check box should be checked by default.

Then there's the topic of "Test merge". I have more or less stopped using it since it does not really provide any time benefit, and the predicted conflicts are mostly greatly exaggerated. Is there really no way to make the test merge more accurate when it comes to predicting conflicts?

- When a Test merge is performed, I would suggest changing from the red "conflicted" to an orange "potential conflict", to highlight that this is only an assumed conflict. The manual clearly states this, but not everyone reads the manual...

I think that was all for now. :-)

Hans-Emil

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2888986

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-29 12:31:25 CET

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.