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

RE: Merge commit message generation bogus

From: Jojakim Stahl <joja.public_at_jojakim.de>
Date: Wed, 21 May 2014 06:08:03 -0700 (PDT)

> While I can reproduce the problem with your script, there's nothing in TSVN we can do to fix it.
> so all we get is the range 'r5 through r7' and TSVN uses the log messages from that range to pre-fill the 'recent messages'. We don't get the info that r6 wasn't really merged.

Hello Stefan,

Thank you for taking the time to investigate the problem.
But I'm not sure that it is impossible to do anything against, because this behavior doesn't show up always like this. I do many, many merges with revision ranges x-y where in-between are gaps (=revs that target unrelated pathes). Most of the time the commit message is setup correctly. There must be some special circumstances where it fails.

Note i.e., that the problem didn't show up when you started on a "prefabricated" repository and you didn't do the commits on the same machine (see my first test case).

Note also, that when you do not enter the Show Log dialog on the merge operations, but accept the preset revision range without confirming them in the Show Log window, the commit message which is build doesn't contain the log text at all.

Personally, I would locate the problem somewhere in the log cache, just a guess. I don't know the source code and so I don't know anything of certitude at all.

Thanks again.

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-05-21 15:08:12 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.