[Top][All Lists]

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

Re: [Monotone-devel] Re: Project separation

From: Stephen Leake
Subject: Re: [Monotone-devel] Re: Project separation
Date: Fri, 05 Nov 2010 07:08:26 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt)

Lapo Luchini <address@hidden> writes:

> Thomas Keller wrote:
>> I already brought up the idea on IRC some time ago - I am looking for a
>> way to restrict allowed incoming revisions on the server-side.
> I've got an idea, which might well be orthogonal to yours (or be the
> same, really?), but could have some use: by default use the branch
> filter only to find the root of the graph, and then bring it all.
> Right now we have a (huge) graph spanning over some 30 branches but,
> since most of them are merged in mainline already, in fact pulling
> "nvm-only" *already* brings in the bulk of most of those branches,
> *except* the branch certificate.
> This way they're not polluting the "mtn ls branches" (which is good) but
> OTOH we're really liars about that, because we *already* have 99.9% of
> the bload of those branches, with the only exception of the name.
> We might thus (as an option, or by default) mean "pull nvm" as "pull the
> ROOT element which was named 'nvm' plus all of its children, in any
> branch whatsoever".
> OTOH if some feature branches are adding huge files and then deleting
> them before mainline landing, we're probably *not* pulling that bulk
> right now; but I wonder how often does that happen in a fairly
> well-behaved project.

There are branches that are not merged to mainline, and probably never
will be; nvm.experimental.win32_pipes, for example.

Those are children of the root of nvm, but are not pulled by "nvm-only".

-- Stephe

reply via email to

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