First impressions (long)

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Westby wrote:
> On Mon Dec 14 23:11:14 +0000 2009 Barry Warsaw wrote:
>> I hadn't thought about putting the debian/ thread at the top, but your use
>> case makes perfect sense.  The reason I had put it right above the upstream
>> baseline thread is because then everything above it is patches, and you
>> wouldn't have to worry as much about where to put your new development
>> threads, or what to do with them once you collapse them into the thread you
>> want to push to the source branch.
>>
>> But I think your use case is more important, though I wonder how easy it will
>> be to submit thread patches upstream out of order and independently, since
>> they'll have all the lower threads mixed in.  Maybe that's not a practical
>> problem though.
> 
> That's the rationale people have for proposing a full DAG of patches.
> 
> I'm not against it in principle, but I would have to see an illustration of
> a UI for it that didn't chill me to the bone.
> 
> Thanks,
> 
> James
> 

What about:

$ bzr show-loom
  Thread       Basis Thread(s)
  integration  feature one, feature-two
* feature one  upstream
  feature-two  add-foobar
  add-foobar   upstream
  upstream

I don't expect these to be terribly complex DAGs, nor to have 1000s of
nodes in them.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkspDx0ACgkQJdeBCYSNAAO6mQCg04pyoCIxG0kDWEhC3C+Zz4L3
ZEsAoJfOnPqkHfP0DPopIk2BF7wPoYKk
=UsoT
-----END PGP SIGNATURE-----