separate tar.* config to its own source file
Even though there is only one configuration variable in the namespace, it is not quite right to have tar.umask described among the variables for tag.* namespace. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 18, 2020 at 11:26 UTC
8312aa7d74d109303c2d0159e5e325f337ddf23e
3 files changed
+8
-7
Documentation/config.txt
+2
@@ -445,6 +445,8 @@ include::config/submodule.txt[]
445
446
include::config/tag.txt[]
447
448
+include::config/tar.txt[]
449
+
450
include::config/trace2.txt[]
451
452
include::config/transfer.txt[]
Documentation/config/tag.txt
-7
@@ -15,10 +15,3 @@ tag.gpgSign::
15
convenient to use an agent to avoid typing your gpg passphrase
16
several times. Note that this option doesn't affect tag signing
17
behavior enabled by "-u <keyid>" or "--local-user=<keyid>" options.
18
-
19
-tar.umask::
20
- This variable can be used to restrict the permission bits of
21
- tar archive entries. The default is 0002, which turns off the
22
- world write bit. The special value "user" indicates that the
23
- archiving user's umask will be used instead. See umask(2) and
24
- linkgit:git-archive[1].
Documentation/config/tar.txt
new
+6
@@ -0,0 +1,6 @@
1
+tar.umask::
2
+ This variable can be used to restrict the permission bits of
3
+ tar archive entries. The default is 0002, which turns off the
4
+ world write bit. The special value "user" indicates that the
5
+ archiving user's umask will be used instead. See umask(2) and
6
+ linkgit:git-archive[1].