[PATCH 3 of 6] phases: add basic pushkey support

[Laurens Holst]

Op 14-12-11 23:43, Matt Mackall schreef:
> Assumption:
> New commits are assumed to be draft regardless of the publish
> setting/default.
>
> (active = "used for local pulls and/or commits, etc., not just pushes")
>
> [...]
>
> Case 3: repo A is active and publishing (questionable user case)

I have another use case for this,

Sometimes when I don’t have access to my development environment and I 
need to fix something (especially when it’s urgent), I SSH directly to 
my server to fix it there and commit the fix.

As the commit appears in the public repository, I think it should be 
marked as public.

I have done this for two of my repositories in particular; these are 
repositories for websites, and I have it set up so that anything you 
push to them automatically becomes live. This works by serving up the 
working copy by Apache, and auto-updating the working copy with an 
incoming hook.

As there is no rigorous testing or staging area, sometimes there is an 
error (e.g. a broken download link for a new software release) that I 
need to fix as quickly as possible after it is noticed. The easiest way 
to do this when I’m not at home is fixing it directly on the 
repository/web server, which I can do in two ways: manually updating to 
an older version (but that would delay the software release), or editing 
the page with the broken link and committing it.

So personally I think that new commits should respect the publish 
setting (and the default should be draft).

~Laurens