Re: Merge commit message generation bogus

On Mon, May 19, 2014 at 8:58 AM, Jojakim Stahl <joja_at_jojakim.de> wrote:

> 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. 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.
>
>
Yes, because then the 'missing' revisions were not in the log cache and
therefore could not be used to generate the log message.

> 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.
>

But still you insist that my analysis was wrong.

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3078834
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].