push aborts for new branch even if no heads

CG Linden cg at lindenlab.com
Fri Nov 13 11:22:40 CST 2009

On Fri, Nov 13, 2009 at 9:02 AM, Jesse Glick <jesse.glick at sun.com> wrote:

> Dirkjan Ochtman wrote:
>> Closed branches should be pushable with no flag at all
>> This works well today, with hg 1.3.1, by using --close-branch and then
>> merging the closing commit into some other branch.
> Assuming "some other branch" means "default", that's no good because it
> makes the default branch dependent on all the closed branches. These are
> probably no longer critical to have except for archival purposes. So if
> someone does 'hg clone -r default' they will get all of these closed
> branches by way of dummy merges.
> I suppose you could have a special branch called "void" whose sole purpose
> was to serve as a (dummy) merge point for closed branches. But it seems
> simpler, nicer, and more intuitive to just close a branch and have it
> disappear from view unless someone is really looking for it.
I definitively would be very unhappy with having to merge closed branches,
as that would break the initial use case that started this thread: "how do I
list all changes since the last release".

Yes, you can prune out the "last release" part, but you would then also need
to prune out all the previous releases (which requires you to remember them

Also, I like how they (the closed heads) stand out in the revision graph. As
a general principle, we should avoid "faking" things just to get a system to
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20091113/b5663c4f/attachment.htm>

More information about the Mercurial-devel mailing list