[PATCH 0 of 6 phases] Secret changeset

[Matt Mackall]

On Mon, 2011-12-19 at 11:46 +0100, pierre-yves.david at logilab.fr wrote:
> 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.

I think this is a little too invasive.

Another alternative is to have a default phase in the config. This will
allow code that wants to temporarily override the mode to do it by
tweaking ui. It'll also allow knowledgeable users to make things work
for them for random commands with --config phases.default=secret.
We do something similar with merge tools and ssh options.

But I think we want to make phases generally work without users needing
to think about them. So for instance, we should have MQ make changesets
secret by default.

Before we go too far down this path though, I'd like to start harvesting
some of the fruits of the efforts you've already made so that we can
start actually using it before it gets baked into a release. For
instance, making rebase and MQ refuse to work on public csets.

-- 
Mathematics is the supreme nostalgia of our time.