[PATCH] bzr whoami

[Aaron Bentley]

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

Robey Pointer wrote:
> I tend to create these little branches for one feature or fix, do  maybe
> a half dozen commits on them as I respond to feedback, and then  once
> (if) they're merged, I blow them away.  Putting them in  launchpad
> implies (to me) that I'll keep these branches around for a  while.
> 
> Am I unusual in working this way?  Is it bad for me to blow away 
> branches after they land?  (My assumption is that the full history is 
> in the main branch after it's merged.)

I keep all my branches.  Some branches go dormant for months, then come
back to life.  Perhaps my branches are slightly more general than yours,
e.g. bzr.ttransform always gets my Tree Transform updates.

It's theoretically possible to more-or-less recreate a branch from a
revision, but I don't think bzr actually does this yet.  Also, you lose
any branch-configuration data like parent, email address and nick.

I don't see why you'd make the effort of deleting branches.  Perhaps
your are using a repository with --trees?  If the only way to keep your
workspace clean is to delete branches, I can understand why you would.

I keep my repo separate from my checkout, so that I can do 'bzr zap' on
dormant checkouts to keep my workspace neat.

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

iD8DBQFEpCwm0F+nu1YWqI0RAtlXAJ9htXO0G7kmr3wb4TIBxYOkVmVGHQCfWV2F
QsYIpUHP5ZFTVRcIFUiuxyM=
=m08d
-----END PGP SIGNATURE-----