bundle command changes phase to public and probably shouldn't

[Matt Mackall]

On Thu, 2012-09-27 at 10:26 -0600, Ethan Barnes wrote:
> In our workflow we have a build server that builds our potential fixes 
> on multiple platforms. A custom extension bundles our changeset(s) up 
> and sends them to the build server. When an error is found, we correct 
> it locally then resubmit to the build server. This may happen several 
> times before a changeset is actually pushed to the master repo.
> 
> The problem is that every time we submit to the build server, the bundle 
> command makes the changes public. Thus, when attempting to correct 
> errors found by the build server, the phase is always "wrong".

This is making the conservative assumption that a bundle effectively
exposes a changeset to the world. The bundle format has no provision for
passing phase information and needs a complex version bump to do so.

Funny, I think we have the opposite behavior on the unbundle side.

> Is there a way to tell mercurial that bundling is not pushing?

I don't think so. Your idea of tying it to publishing=False might be
good.

-- 
Mathematics is the supreme nostalgia of our time.