From: Jonathan Tan Date: Mon, 08 May 2017 21:33:50 GMT Subject: [PATCH v2 1/2] docs: correct receive.advertisePushOptions default Message-ID: <3d79124df1e235e1819cf16a41ecec27391f8609.1494279020.git.jonathantanmy@google.com> In-Reply-To: In commit c714e45 ("receive-pack: implement advertising and receiving push options", 2016-07-14), receive-pack was taught to (among other things) advertise that it understood push options, depending on configuration. It was documented that it advertised such ability by default; however, it actually does not. (In that commit, notice that advertise_push_options defaults to 0, unlike advertise_atomic_push which defaults to 1.) Update the documentation to state that it does not advertise the ability by default. Signed-off-by: Jonathan Tan --- Documentation/config.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 475e874d5..3a847a62e 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -2620,9 +2620,8 @@ receive.advertiseAtomic:: capability, set this variable to false. receive.advertisePushOptions:: - By default, git-receive-pack will advertise the push options - capability to its clients. If you don't want to advertise this - capability, set this variable to false. + When set to true, git-receive-pack will advertise the push options + capability to its clients. False by default. receive.autogc:: By default, git-receive-pack will run "git-gc --auto" after -- 2.13.0.rc1.294.g07d810a77f-goog