[PATCH] bzr whoami

[Robey Pointer]

On 29 Jun 2006, at 2:12, Robert Collins wrote:

> On Wed, 2006-06-28 at 22:52 -0700, Robey Pointer wrote:
>> I spent some time today fixing up my ancient 'whoami' patch to fit
>> the current bzr.dev trunk.  The patch adds:
>>
>> 	* bzr whoami <identity> -- to set your global id
>> 	* bzr whoami --branch <identity> -- to set your id just on this  
>> branch
>> 	* unicode-safe identity
>>
>> Since I first did this patch, John's encoding work has landed, which
>> helped immensely.  Making 'whoami' work with encodings worked with
>> very little new code.  So most of the patch now is moving the
>> blackbox tests (and adding more).
>>
>> I made a temporary branch for this:
>> 	http://www.lag.net/~robey/code/bzr.dev.whoami
>
> For things that are not trivial branches, I'd love to see them being
> registered at https://launchpad.net/products/bzr/+branches with their
> status set appropriately - i.e. 'development' while its being  
> prepared,
> 'mature' when you want it merged, 'merged' after its been merged.

This brings up a question about workflow:

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