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

Stop creating mergeinfo on COPY (was: Problems reintegrating the issue-2843-dev branch)

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 12 Nov 2008 09:50:14 -0500

On Fri, Nov 7, 2008 at 7:10 PM, Paul Burba <ptburba_at_gmail.com> wrote:

> REALLY FIXING THE PROBLEM:
>
> Stopping all the WC-to-WC production of needless explicit mergeinfo
> would go a longggg way to avoiding this, but that doesn't help those
> (including us) with lots of historical subtree mergeinfo. More and
> more I think that copy and move (all, not just WC-to-WC) should never
> produce mergeinfo on the destination *unless* the source has it. It
> can't be worse than what we deal with now...

I propose we just do this ... now. Let's just rip this code out of WC
to WC copy. Do not create mergeinfo when copying stuff. Forget about
making it smarter, let's just stop doing it. The problems we have
created by doing this are far worse than the theoretical problems we
could prevent by getting it right.

Ripping this out will make our product better now and reduce user
frustration. If the theoretical problems turn into real problems and
if someone is motivated enough to put this code back then they can do
so in a way that gets it right.

Let's stop the madness. If this one feature had not been put into
1.5, then most of the problems relating to mergeinfo handling we
complain about would not even exist.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-12 15:50:34 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.