mercurial-phases

How can I tell mercurial that a remote server (on bitbucket for example) is non-publishing when I do not have access to the remote .hg/hgrc file? Background Recent versions of mercurial has a concept of phases that allow one to keep track of which changesets have been shared ( public ) and which ones have not ( draft ). Repository changing operations like rebase are allowed on draft changesets, but not public changesets as others might depend on the latter. Pushing changesets to a public server will change their phase to public by default, but if the server is private or dedicated to code

How can I hinder mercurial from putting changesets to phase “public” on push operations? I want them to stay “draft”. I rebase and histedit a lot, and the repository I push to is for me only. And having to change the phase all the time is a nuisance. What the documentation does not clearly reveal is: The phase-change on push is not a purely local decision. – After “uploading” the changesets, the client asks the server for updates regarding the phases of the commits, and the server is usually telling that they are now “public”. Thus, the .hgrc -snippet [phases] publish = False has to be put on

That may look paradoxical, I know that secret changesets are meant to be private, but what if I want to backup those secret changesets? I work with some branches in parallel and sometimes I want to push one, but not the others. To achieve that, I work in separate clones but I hate that. So now mercurial has phases, I can make secret branches and have everything in the same repository. The problem is that between the beginning of the secret branch and its publication, I want to backup those secret changesets (I have a clone in another machine just to hold my backups in case something happens

We have a code review repository where people hg push -f all sorts of stuff. After reviews are complete, we pull from the project's central repository, rebase, and push. I recently upgraded to mercurial 2.1 and get this message: abort: can't rebase immutable changeset 43ab8134e7af (see hg help phases for details) when I try to hg pull --rebase from the central repository. How do I fix it? nmichaels In the review repository's .hg/hgrc file, add these lines: [phases] publish = False The problem is due to a new feature in mercurial 2.1 called phases . It's great. Here is a nice introduction to