| commit | b7b744f297b736c51636407f5883b3777bb36433 | |
| author | Jonathan Tan <jonathantanmy@google.com> | |
| Mon, 8 May 2017 21:33:50 +0000 (8 14:33 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 9 May 2017 03:11:44 +0000 (9 12:11 +0900) | ||
| tree | ff33911235b81e595a853d31f281affe4845817e | treesnapshot (tar.gz zip) |
| parent | 49800c940790cc7465d1b03e08d472ffd8684808 | commitdiff |
docs: correct receive.advertisePushOptions default
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 <jonathantanmy@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
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 <jonathantanmy@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/config.txt | diffblobblamehistory |