Recipes vs. Looms vs. pipelines

Robert Collins robert.collins at canonical.com
Mon Jan 4 23:34:06 GMT 2010


On Tue, 2009-12-15 at 11:15 -0600, John Arbash Meinel wrote:
> 
> 
> Which (IMO) is something that pushes for having a real DAG in the loom
> state, rather than just a stack model. As it means you can push *just
> this thread* into upstream, and have them merge it, without them
> having
> to merge all of your other changes. Otherwise the loom is just there
> to
> help you develop the patch. And then you throw away all the history
> once
> the patch gets applied to upstream. 

I'm not quite sure what you mean by this. The relationship between
threads being DAG | sequence won't affect what merges are needed.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20100105/4be73d7e/attachment.pgp 


More information about the ubuntu-distributed-devel mailing list