On Fri, Feb 29, 2008 at 10:24 AM, Blair Zajac <blair_at_orcaware.com> wrote:
> Mark Phippard wrote:
> > On Fri, Feb 29, 2008 at 1:17 PM, Blair Zajac <blair_at_orcaware.com> wrote:
> >> C. Michael Pilato wrote:
> >> > NOTE: Everyone will need new working copies after the cutover --
> >> > history has been munged. Also, folks who've been using svnsync to
> >> > mirror the repositories will need to start anew with fresh mirrors.
> >>
> >> What do you mean by "history has been munged"?
> >
> > He is making changes to properties as part of the merge process
> > (changing history). We do not have a mechanism for conveying this to
> > the working copy (one of the problems svn obliterate would also have
> > to solve).
> >
> > Specifically, as revisions are synched he is:
> >
> > 1) Ignoring/stripping any svn:mergeinfo properties
> >
> > 2) Converting any svnmerge properties to svn:mergeinfo properties.
>
> I see, that type of history munging.
>
> Doing the cutover to the new collab.net 1.5 repository should be done with an
> 'svnadmin upgrade' though, right? Not with a custom svnsync copied repository,
> since nobody else will be doing that style of upgrade. This is just a measure
> for testing.
I assume Mike will be releasing his code and recommending it as the
upgrade path for other svnmerge.py users...
--dave
--
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-29 19:30:38 CET