[PATCH 0 of 6 phases] Secret changeset

[Pierre-Yves David]

On Thu, Dec 22, 2011 at 02:24:16PM +0100, Angel Ezquerra wrote:
> > 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.
> 
> I went through that page and I am not sure I fully understand. In
> particular I am confused where it says that:
> 
> "Setting a repository as "publishing" alter its behavior **when used
> as a server**: all changesets are **seen** as public changesets by
> clients."
> 
> If clients see _all_  changesets as public, and you push a draft
> changeset to a non-publising repo, a client pulling from that
> non-publishing repo will get those draft changesets as public?

No.

> > The "Setting a repository as "publishing" alter its behavior **when used as a server**

You only get the altered behavior if the remote is publishing.


> a client pulling from that non-publishing repo will get those draft
> changesets as public?

a client pulling from a **non-publishing** repo see content in they real phase.

* draft changeset are pulled as draft.
* public changeset are pulled as public.


-- 
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/3d0d2bfe/attachment.pgp>