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

Re: RFC: Cleanup some of the mergeinfo madness in our own repos

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 14 Nov 2008 08:36:08 -0500

On Fri, Nov 14, 2008 at 6:24 AM, Paul Burba <ptburba_at_gmail.com> wrote:
> Now for the specifics. I'd like to do one commit that simply removes
> all subtree mereginfo on trunk and our release branches.

I assume you meant to say "feature" branches here and not "release"
branches? In which case I am +1. I do not think we should touch the
release branches and if we do, we would at least need to preserve the
subtree mergeinfo on things like CHANGES and COMMITTERS where it is

On Fri, Nov 14, 2008 at 7:41 AM, Stefan Sperling <stsp_at_elego.de> wrote:

> How much of a problem is it when we use non-trunk builds?
> I usually use the latest 1.5.x against our repo but would use
> a trunk build if that helps with not having to clean up mergeinfo
> every two weeks...

You should be able to use 1.5.x builds with the exception being if you
use it for a WC to WC copy it will create mergeinfo. But we could
just clean it up if this happens.

A question I should probably raise separately but will do so here, is
whether we should propose the reintegrate and copy changes for
backport? I tend to think we should as these directly effect the #1
issues that have been reported since 1.5 was released.

Mark Phippard
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-14 14:36:25 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.