[PATCH 2 of 2] push: introduce --readonly to make push behave more like pull

[Mads Kiilerich]

On 08/23/2016 03:49 PM, Augie Fackler wrote:
>> I don't know if this feature I'm asking for most correctly is described as
>> non-locking and thus readonly and not modifying state or publishing, or if
>> it non-publishing and thus readonly and with no need for locking. It could
>> be described either way - I just want one of them ;-)
> I think the latter is more sensible from a user perspective - the user
> doesn't (ideally) know about or care about our locking requirements,
> so the visible side effect to them (no phase changes) seems like the
> thing to focus on from a UI level.

It is however (in the situation) very visible and annoying for the user 
that push is locking the source repo.

For many use cases, phase change (publish on push) is really not 
relevant. For example when you are propagating a mainline / upstream 
repo to a mirror and everything already has been published.

/Mads