bound branch annoyances

[Aaron Bentley]

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

Marius Kruger wrote:
>     If you uncommit in a checkout, you should expect to
>     uncommit the revision from the branch you checked out.  Where else could
>     you uncommit from?
> 
> 
> The problem is when you are constantly switching between "heavyweight
> checkouts"
> and distributed branches, you never know which one you are dealing with,
> (unless you check with 'bzr info' of coarse)

I think the current bzr info output is too verbose.  If it printed:
  Checkout (heavyweight) of /home/abentley/bzrrepo/bzr.ab

  Parent branch: http://aaronbentley.com/bzr/dev
  Submit branch: /home/abentley/bzrrepo/bzr.dev

I might be more inclined to use it.

> thus its easy to uncommit something you actually just wanted to do locally
> (this actually happened when we temporarily wanted to uncommit something
> to check
> if some problems were caused by the latest revision. In this case we could
> not readily get the original committer to get the commit again:( )

Usually, the best way to do this is with "bzr revert -r".  That won't
lose data regardless of whether you're bound or unbound.

But if you've done this, and you know the revision-id you uncommitted,
you should be able to restore it with 'bzr pull -r revid:$REVID .'
(Maybe we should add that to the uncommit output).

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

iD8DBQFFZIQ20F+nu1YWqI0RAk3DAJ0Ti0vHzEgF0fslQ5rJRfmbuN1P+gCfQw4j
s2C32kx0uxwm74yWTC+c6Y8=
=Jwr7
-----END PGP SIGNATURE-----