Merge commit message generation bogus
From: Jojakim Stahl <joja.public_at_jojakim.de>
Date: Mon, 28 Apr 2014 01:55:41 -0700 (PDT)
Hello,
TortoiseSVN 1.8.6, Build 25419 - 64 Bit , 2014/04/12 11:40:48
and have the following problem:
I want to merge from one directory to another two Revision which apear in the log Dialog for selection of the revisions to merge one after the other:
10935 Text 2
That means no commits between the two Revisions are targeting anything in the merge source Directory.
I select these two revisions and tortoisesvn puts in the TextBox specifying the revisions to merge:
10895-10935
This seems ok to me. I do the merge, the merge result appears to be OK. When I want to commit the merge, I want to select the log text from recent Messages. The first entry, which should correspond to the latest merge is shown as a blank line - the first Problem. However, I choose this line and the text which is inserted in the log message text box of the commit Dialog contains between the to logs that I expect a bulk of logs unrelated to my merge. This is the second Problem.
I tested now to Change the specified Revision range to merge to enumerate the two specific Revision explicitly (note the comma instead the dash):
10895,10935
When I do the merge like this, the composed log message for the commit is OK, no blank line, no additional log texts.
I am not 100% sure, but 90%, that this behavior has been introduced with the latest update I installed. I can't tell any more the Version I used before, but it was 1.8.x.
Can anyone confirm this to be a bug? Is this a known Problem? Should I file a bug Report to the tracker?
-- Joja ------------------------------------------------------ http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3077149 To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].Received on 2014-04-28 11:10:01 CEST |
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.