gnu-arch-users
[Top][All Lists]
Advanced

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

Re: [Gnu-arch-users] NEW POLICIES (draft)


From: Aaron Bentley
Subject: Re: [Gnu-arch-users] NEW POLICIES (draft)
Date: Mon, 04 Oct 2004 14:59:47 -0400
User-agent: Mozilla Thunderbird 0.5 (X11/20040309)

Andrew Suffield wrote:
On Sat, Oct 02, 2004 at 03:11:47PM -0700, Thomas Lord wrote:

** The Solution: Cascade Branches

There is a simple and elegant solution to the problem with long term branches and that is to use "cascade branches",
 as illustrated in ./cascade.ps.


On reflection, this is just a prism structure under a different name,
plus a rule that there must be a single line of ancestry through all
of them (which is actually useless and should be ignored - this isn't
used for anything, so regular freeform prism structure will work just
the same; the freeform structure is just a set of 'cascades' anyway).

The single-line-of-ancestry rule means it's not a prism.

If I understand it correctly, the idea is that merges happen this way:

upstream -> foo--0 -> foo--1 -> foo--2
etc.

Note that in the example, direct merges to tla--longterm.X.Y.0.1 happen only after tla--longterm.X.Y.0.0 has been merged into tla--devo--X.Y

This is what we've been doing for years, nothing to see here, move
along...

Even if so, having a label to hang on this pattern is useful.

Aaron

--
Aaron Bentley
Director of Technology
Panometrics, Inc.




reply via email to

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