monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] Re: Project separation


From: Lapo Luchini
Subject: [Monotone-devel] Re: Project separation
Date: Thu, 04 Nov 2010 18:37:01 +0100
User-agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.15) Gecko/20101102 SeaMonkey/2.0.10

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.

-- 
Lapo Luchini - http://lapo.it/




reply via email to

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