[PATCH 0 of 3] An attept at branch closing

[Sune Foldager]

On 05/10/2008, at 10.27, Martin Geisler wrote:

> Sune Foldager <cryo at cyanite.org> writes:
>> 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.

I assume that that means keep one of the versions, tossing away the  
other one. In that case, yes, that would be a viable solution I guess.  
Maybe a bit "hi tech" for the average mercurial user, though. For my  
use, I can just wrap it in a script; I have several things wrapped  
already.

-- Sune.