[PATCH 0 of 6 phases] Secret changeset

[Pierre-Yves David]

On Thu, Dec 22, 2011 at 12:35:39PM +0100, Angel Ezquerra wrote:

> > I think the setup below may become common once people get used to mutable
> > mercurial:
> >
> >    Two central repositories:
> >
> >    * A non-publishing one where every body can push
> >
> >    * A publishing one where reviewer can push with enough care and security to
> >      be sure to only push what they have reviewed.
> >
> > Phase hooks should play a big role in making sure changeset are not made public by mistake.
> 
> That is perhaps what I had missed. I thought that pushing to _any_
> repo would always make the changesets public (i.e. take them out of
> the draft phase). Are you saying that is not the case?

server repository can be either publish or unpublishing. only changeset pushed
to publishing server are made public.

See http://selenic.com/hg/rev/218ec96c45d7 for details

Publish is default for backward compatibility reason. People playing with
mutable history will want all dev to turn it to False on they developement
repository.

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111222/bbdd6bb6/attachment.pgp>