[PATCH 6 of 6] check-concurrency: expose the feature as 'server.check-concurrency'

[Augie Fackler]

> On Jun 11, 2017, at 16:48, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> 
> I slept over this before sending an updated patch and I think there is small bit still missing. The latest proposal is a bit ambiguous in term of value meaning.
> 
> The initial proposal had a "verb" and an "object":
> 
>  check-concurrency=stric # "check" is "strict"
>  check-concurrency=related # "check" if "related".
> 
> The latest one is a bit less clear, since we kinda lost the
> "verb".
> 
>  concurrent-push-mode=strict # "mode" is "strict" (okay)
>  concurrent-push-mode=related # "mode" is "related" what does this mean?
> 
> Maybe we should switch the "logic" of the "value":
> 
>  concurrent-push-mode=related # "unrelated" push can be concurrent
> 
> Or makes it more verbose:
> 
>  concurrent-push-mode=allow-unrelated
> 
> (or)
> 
>  concurrent-push-mode=deny-related
> 
> What do you all think?

That seems like an improvement to me.