RFC: Initial branch operation order

Wed Apr 27 17:05:24 UTC 2011

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

On 11-04-27 12:54 AM, Robert Collins wrote:
> Its probably possible to make the code simpler by using a null object
> or something, but I have no passionate attachment to the object
> creation order (with one caveat, we shouldn't show bogus objects like
> a branch with the tip not being in the repository at any point in
> time).

It might be interesting to have an "incomplete" state for branches.  If
the creation was interrupted, accessing it (other than with push/branch)
would raise a BranchIncomplete error (a subclass of NoSuchBranch).

This could be represented on disk by storing it as
.bzr/incomplete-branch, and then renaming it to the normal location when
complete.

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

iEYEARECAAYFAk24TNQACgkQ0F+nu1YWqI05/gCfbEVP/CJ2bnVB/PQaWimwfqZD
394AmgMaopcqHM0+065a4DCElkpFD52r
=PQzi
-----END PGP SIGNATURE-----