Launchpad logo and name.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index ][Thread Index ]

Re: [Launchpad-users] Best Practice for Merged Branches



On Sun, 25 Oct 2009 23:33:54 Jonathan Lange wrote:
> On Sat, Oct 24, 2009 at 11:13 PM, Charlie Poole <charlie@xxxxxxxxx> wrote:
> > Hi,
> >
> >> > Once a public feature branch is merged into trunk, and there is no
> >> > further development being done on it, do people generally
> >>
> >> clean them out - i.e.
> >>
> >> > remove them?
> >>
> >> Launchpad automatically marks them as Merged and then hides
> >> them on the user interface by default. I don't know many
> >> people who delete them though.
> >
> > OK...
> >
> >> For local copies of branches, I delete them when they are
> >> merged. I wrote a plugin to make this easier, which you can
> >> find at lp:bzr-removable.
> >
> > My working trees are separate from my shared repository, so I
> > can easily delete them. Can I safely delete the branch
> > subdirectories in the repository as well?
> 
> You can safely. However, if your working trees are separate from your
> branches, I'd just leave the branches there. They don't take up much
> room, probably don't clutter the directory listings you are interested
> in, and might be handy to have in the future.

This is exactly what I do.  I remove the working trees for the branches that 
have merged, and leave them in the repo as I (almost) never do directory 
listings there.

Tim



This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.

(Formatted by MHonArc.)