[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Re: mtn:// sync

From: Markus Schiltknecht
Subject: Re: [Monotone-devel] Re: mtn:// sync
Date: Sat, 29 Mar 2008 16:12:47 +0100
User-agent: Mozilla-Thunderbird (X11/20080109)


Stephen Leake wrote:
Logically, those are not "branches"; they are now part of mainline. So
it would be more correct to say :

I don't quite follow your reasoning here. Even if they got merged later on, those are still "branches of development".

>     You will get revisions that used to be on a branch but are now on
>     mainline.

Their branch cert didn't change. Even after a merge, most revisions of the branch will still carry only *one* branch cert - that of the branch. Thus I fail to see how those should now "be on mainline".

You'd only save sync'ing 'new' development branches.

Which is a good thing.

Really? If I'm interested enough in a project to want to fetch it's development history (!), I'm at least as interested in all current branches, as I am interested in history. I've never taken the effort to strip away branches I might not be interested in (heck, how should I even know?).

But that's just me. Let's hear other people's preferences here!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]