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

Someday we'll have merge tracking [was Re: svn commit: r17771 - branches/bdb-fixes/tools/dev]

From: Michael Brouwer <mb.7766_at_gmail.com>
Date: 2005-12-23 19:29:01 CET

On 19 Dec 2005 11:03:02 -0600, kfogel@collab.net <kfogel@collab.net> wrote:
> Any objection if changes like this start life on trunk?
> It's not a big deal. If it would slow you down then I'd say it's not
> worth it. But if it's the same either way, then non-branch-specific
> change like this should go to trunk first. (Someday we'll have merge
> tracking and it'll matter! :-) ).
> -Karl

I'd hope that when the day comes on which svn finally has merge
tracking it wouldn't matter where a change started out. You should be
able to merge in either direction.

Currently with svk merge tracking it's actually better to make changes
to the release branch first and then merge them to the trunk rather
than vice versa. (Since the latter would pull all trunk changes into
the release branch). In order to grab just particular changes from
trunk into a release branch you'd need cherry picking support in
addition to merge tracking.

Received on Sun Dec 25 02:50:42 2005

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.