[RFC] Represent Loom threads using branches

[John Arbash Meinel]

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

Aaron Bentley wrote:
| I've been using the loom plugin pretty heavily, and I still feel like
| loom threads should be branches.
|
| branches
| 1. have a last-revision pointer
| 2. have configuration data
| 3. have a physical location in URLs and on filesystems
|
| threads
| 1. have a last-revision pointer
|
| Threads don't have anything that branches don't have.  They lack a
| location, and they lack configuration data.
|


I think it would be interesting to have looms use real branches. I know we've
discussed having the threads accessible by URLs (which does not mean they have a
location on disk). Such as "http://path/to/branch#thread", etc.

I do think it is reasonable for them to have a different default push/pull
location. Since that (as you mention) makes it easy to keep a couple different
threads that are actually different upstream locations.

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

iEYEARECAAYFAkgY4mIACgkQJdeBCYSNAAMIoQCeJTYDPSKZskkWpbtqlpEr84x1
YqIAnixT1DoZHvDhC2VrAEdIaat8vmTF
=rZEY
-----END PGP SIGNATURE-----