preparing migration from baz to bzr

[Aaron Bentley]

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

John Arbash Meinel wrote:
> Also, after we get writeable remote branches, I'm planning on working on
> "bound branches" such that when you run "bzr commit" if the branch is
> bound, it commits to the remote branch first, and then to the local
> branch.

Just a heads-up, I'm working on centralized storage now, and I plan to
support the bound-branch workflow.

The main differences between bound-branch and implicit/branching are
- - bound-branch will not auto-create a new remote branch if the local one
is out-of-date
- - Branch.revision_history() will truncate its output to stop at the
local last-revision
- - Branch.append_revision() will operate only if
  a. You're out-of-date, and you're appending the revisions that appear
in the true revision history (e.g. pull)
  b. You're up-to-date (e.g. commit).
Branch.append_revision() will fail if you are out of date and attempt to
commit.  We can detect this early, but even it we didn't, we'd still be
correct.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDVPov0F+nu1YWqI0RAgWoAJ0aeRxyrSWE8P/uanEdy3BFrFPA7gCffZvf
uAnueECKt0zcpNp27uJuXgQ=
=UtDs
-----END PGP SIGNATURE-----