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

Re: Merge Log Template is not saved

From: Martin Bischoff <tinu44_at_gmail.com>
Date: Tue, 23 Jul 2013 16:37:34 +0200

BTW: the problem is also reproducible in TSVN 1.8.1.

On Tue, Jul 23, 2013 at 1:36 PM, Martin Bischoff <tinu44_at_gmail.com> wrote:

> I was trying to use the Merge Log Template feature in TortoiseSVN 1.8.0,
> but the template is not saved when I close the edit-dialog.
>
> Here are the steps to reproduce the problem:
> - on the working copy root directory select TortoiseSVN->SVN Properties
> - select New -> Merge Log Templates
> - enter the templates.
> - Click OK
> - Now, double click the tsvn:mergelogtemplatetitle row again in teh
> Properties dialog
> --> the first template string (title-string for merge) is still there, but
> the template for each merged revision is lost.
> --> if I commit the property-change, and then check again, the text is
> still missing
>
> Don't know if this is relevant, but these are the texts I entered in the
> three text-areas (without double-quotes, \n is a line-break):
> - "Merged revision(s) {revisions} from {mergeurl}:\n"
> - ""
> - "r{rev} ({author}):\n{msg}\n"
>
> System information:
> - Windows 7 Enterprise, 64 bit
> - TortoiseSVN 1.8.0, Build 24401 - 64 Bit , 2013/06/17 18:15:59
>
> Best regards,
> Martin
>
>
> PS: two related questions:
>
> - when using the standard repository layout (/trunk, /branches, /tags),
> where should the merge log template property be set? on the repository
> root, on trunk or on branches? Or on any folder, where we merge to?
> - must the property be set recursively?
>
>
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3061097

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-07-23 16:37:43 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.