Closed GoogleCodeExporter closed 9 years ago
This seems related to issue #361: instead of using the 'record only'
notifications unconditionally, we should only use them if the merge is actually
done with 'record only'.
Original comment by tortoisesvn
on 6 Mar 2014 at 8:28
This issue was closed by revision r25273.
Original comment by tortoisesvn
on 7 Mar 2014 at 6:12
This issue was closed by revision r25274.
Original comment by tortoisesvn
on 7 Mar 2014 at 6:17
I'm still experiencing this issue.
TortoiseSVN 1.8.8, Build 25755 - 64 Bit , 2014/08/10 14:44:06
Original comment by stanley....@gmail.com
on 3 Dec 2014 at 7:51
Fixed only in trunk ATM (1.9) according to
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=30956
95
Download nightly at http://nightlybuilds.tortoisesvn.net/latest/x64/full/
Original comment by ndhm...@gmx.de
on 1 Feb 2015 at 12:30
I have the same issue with TortoiseSVN 1.8.10, Build 26129; having to build my
own command-line script to circumvent this annoyance.
It might not seem like much, but using JIRA connector (or any bugtracker
connector that relies on the comment content) means that merge could improperly
flag JIRA # as being part of the merge ...
Original comment by sberthia...@gmail.com
on 12 Mar 2015 at 12:55
Original issue reported on code.google.com by
tortoisesvn
on 6 Mar 2014 at 7:22