[PATCH 0 of 3] An attept at branch closing

[Martin Geisler]

Sune Foldager <cryo at cyanite.org> writes:

> On 04/10/2008, at 23.33, John Mulligan wrote:
>> On 2008-10-04 5:03:44 pm Martin Geisler wrote:
>>> I have not used named branches for anything myselves, but from
>>> playing around with them I'm surpriced that adding
>>>
>>>  [defaults]
>>>  branches = -a
>>>
>>> to your .hgrc file does not suffice. It will make 'hg branches'
>>> output only branches which are not yet merged.
>>
>> If I understand it right, I don't think these features cover the same
>> thing. The branches we want closed do have unmerged heads, and do
>> show up when the - a option is used.
>
> Yes, I also plan on using mercurial in scenarios where we might have
> several unmerged branches that we won't be using anymore. Of course
> one could always do a bogus merge into some other branch to get rid of
> it, but that isn't too cool either.

Why not? Doing a merge signals that this line of development is finished
(at least temporarely). So when you decide to abandon a named branch it
seems reasonable to me that you must you "wrap things up" by merging it
with 'internal:local' as the merge program.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20081005/cf03f747/attachment.asc>