| commit | a812789c264b1cabd8e5a22b410a9004781a81c9 | |
| author | Patrick Steinhardt <ps@pks.im> | |
| Fri, 9 Apr 2021 11:27:52 +0000 (9 13:27 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 11 Apr 2021 06:03:19 +0000 (10 23:03 -0700) | ||
| tree | d1aaf94577e133a2ffa0aa0775250d2cfdd8e1de | treesnapshot (tar.gz zip) |
| parent | 89b43f80a514aee58b662ad606e6352e03eaeee4 | commitdiff |
uploadpack.txt: document implication of `uploadpackfilter.allow`
When `uploadpackfilter.allow` is set to `true`, it means that filters
are enabled by default except in the case where a filter is explicitly
disabled via `uploadpackilter.<filter>.allow`. This option will not only
enable the currently supported set of filters, but also any filters
which get added in the future. As such, an admin which wants to have
tight control over which filters are allowed and which aren't probably
shouldn't ever set `uploadpackfilter.allow=true`.
Amend the documentation to make the ramifications more explicit so that
admins are aware of this.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When `uploadpackfilter.allow` is set to `true`, it means that filters
are enabled by default except in the case where a filter is explicitly
disabled via `uploadpackilter.<filter>.allow`. This option will not only
enable the currently supported set of filters, but also any filters
which get added in the future. As such, an admin which wants to have
tight control over which filters are allowed and which aren't probably
shouldn't ever set `uploadpackfilter.allow=true`.
Amend the documentation to make the ramifications more explicit so that
admins are aware of this.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/config/uploadpack.txt | diffblobblamehistory |