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

Re: Why Merge-Tracking is disabled?

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 9 Mar 2009 16:05:40 -0400

On Mon, Mar 9, 2009 at 14:41, Harald Hoyer <hahoyer_at_t-online.de> wrote:
> Merged two branches, but merge tracking did not work. Couldn't find any
> reason.
> After desperate efforts I more or less accidentially used the "Only record
> the merge"-option. Now I could see an error message: "Merge from foreign
> repository is not compatible with mergeinfo modification". And the reason of
> the trouble was: on checkout I used a different case to specify the
> svn-server-name (example: "svn://MyServer/repo1/trunc" and
> "svn://Myserver/repo1/branch/v11").
> First wish: It should be easier to find out, why merge tracking did not
> work.

Merging between repositories doesn't work (or isn't supposed to). I
believe this is already documented. Subversion thought you were going
between repositories.

> Second wish: At least the server name part should not be considered as case
> sensitive.

Subversion is case-sensitive everywhere. You'd have to take this issue
up on the Subversion mailing list.

> Third wish: To avoid a messy and disturbing situation, it should be possibe
> to protect against merges without merge tracking.

Messy in what way? I suspect this would go back to the SVN libraries as well.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-09 21:05:53 CET

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.