[PATCH] bzr whoami

[Martin Pool]

On 29 Jun 2006, Robey Pointer <robey at lag.net> wrote:
> 
> On 29 Jun 2006, at 12:28, John Arbash Meinel wrote:
> 
> >>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.
> >
> >Also, I should mention that the 'launchpad' plugin is now bundled with
> >bzr, so registering a branch should be as simple as:
> >
> >bzr register-branch http://public/location --project bzr
> 
> Well in that case... done. :)
> 
> Hopefully there'll be a way to remove it later?

Yes, there's an outstanding bug asking for a way to remove them.  As you
just demonstrated if people can't remove them (or at least
deactivate/hide them) they'll be reluctant to put them in.

> Right now I'm probably using repos in a weird way because I don't  
> fully understand them.  I have a repo here:
> 	~/code/bzr/
> and I keep branches here:
> 	~/code/bzr/bzr.dev/
> 	~/code/bzr/bzr.dev.whoami/
> and when I create them, I go in and do 'bzr checkout' so they'll have  
> a working tree.

I have a similar setup.  When I want to clean up, I do 'bzr missing
--mine-only' to check if there's anything left unmerged to main and if
that's empty then I delete them.  (Perhaps something like that could be
put into bzrtools zap.)

> Anyway part of the paradox of Robey is that my computer room is a  
> giant pile of trash, but I'm really anal about keeping my disk  
> organized and uncluttered.  I see 5-6 open bzr branches and think "I  
> should clean these up and get them merged or delete them".  For no  
> other reason than it starts to seem cluttered to me to have a handful  
> of code folders that I'm not actively working in.

What I'd like to get to with the registry on launchpad is a similar list
across the whole project:

 * these branches need to be reviewed or merged.. and here are comments
   from various reviewers and a summary of the outcome
 * these branches have ongoing interesting development but aren't ready
   for merge yet
 * these branches might be interesting but the author seems to have
   abandoned them
 * these branches existed a while ago but they were abandoned or totally
   merged or whatever, so they're hidden by default

-- 
Martin