[PATCH] bzr whoami

[John Arbash Meinel]

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

Robey Pointer wrote:
> 
> On 29 Jun 2006, at 2:12, Robert Collins 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.)
> 
> Or is it more that posting branches to launchpad is a good way to bring
> them to everyone's attention, no matter how short-lived they may be?  In
> which case I'm happy to try to do that.
> 
> robey


I think there are a few reasons:

1) If your server goes down, we have a mirror
2) It is an aggregation point which makes it easier to find a branch
rather than searching around for each person's personal server
3) Canonical wants to waste your bandwidth trying to pull branches that
don't exist anymore. :) (I don't know if there would be some way to tell
LP that I *removed* this branch, you can keep it, but stop mirroring me).

I think your workflow is great. Feature branches are very good things.
Lets have more. :)
But really, 1 and 2 are reasonably important. I don't think much
bandwidth is consumed just probing for .bzr/branch-format, so 3
shouldn't really be an issue. Though you may see them show up in your
HTTP logs.

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

iD8DBQFEpClUJdeBCYSNAAMRArhoAJ4wvepptD2psW62xoC1RbGnTzQ9wACcD79I
Aj4tNTfj+wmqh2JkpFIOz2I=
=2GlS
-----END PGP SIGNATURE-----