[PATCH 0 of 6 phases] Secret changeset

[Laurens Holst]

Hey,

I saved up two questions re. secret changesets:

1. If I commit on top of a secret changeset, will the new changeset be 
draft or secret?

2. If I push a changeset B whose parent is A to a repository which has a 
changeset C whose parent is also A, will it abort due to the multiple 
heads or not?

~Laurens

Op 19-12-2011 11:46, pierre-yves.david at logilab.fr schreef:
> This series implement secret changeset logic.
>
> Secret changeset are kept local and never exchanged.
>
>
> The only way to create a secret changeset for now is to add a --secret switch to
> commit. The same patch add a new secret parameter to internal machinery. This
> addition have a huge impact on extension but I could find another solution as
> clean.
>
> We'll probably want simillar switch on unbundle and import but this series focus
> on getting the internal mechanism in place.
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>


-- 
~~ Ushiko-san! Kimi wa doushite, Ushiko-san nan da!! ~~
Laurens Holst, developer, Utrecht, the Netherlands
Website: www.grauw.nl. Working @ www.roughcookie.com


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4332 bytes
Desc: S/MIME cryptografische ondertekening
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111219/c095c5ef/attachment.bin>