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

Log message source priority

From: Alexander Klenin <klenin_at_gmail.com>
Date: Sun, 27 Jan 2008 01:03:56 +1000

On Jan 26, 2008 10:30 PM, Alexander Klenin <klenin_at_gmail.com> wrote:
> By the way, what should TortoiseProc /command:commit do if
> passed both /logmsg and /logmsgfile?
> 1) Silently use /logmsg, discard /logmsgfile
> 2) Silently use /logmsgfile, discard /logmsg (current behavior)
> 3) Fail with error message (I think this is best option)
> 4) Concatenate them (most trivial fix).

Hm, actually it is more complex than that.
All message sources are now prioritized as following:

1) tsvn:logtemplate
2) /logmsg
3) /logmsgfile
4) %MESSAGEFILE% from start-commit hook

Each source, if present, silently overrides previous one.
In some cases, especially with (4), it even makes sense ;-)
So perhaps this should be documented and left as-is?

Alexander S. Klenin
Insight Experts Ltd.
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-01-26 16:04:02 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.