Skip to content

Commit 8312aa7

Browse files
committed
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 <[email protected]>
1 parent 0822e66 commit 8312aa7

File tree

3 files changed

+8
-7
lines changed

3 files changed

+8
-7
lines changed

Documentation/config.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -445,6 +445,8 @@ include::config/submodule.txt[]
445445

446446
include::config/tag.txt[]
447447

448+
include::config/tar.txt[]
449+
448450
include::config/trace2.txt[]
449451

450452
include::config/transfer.txt[]

Documentation/config/tag.txt

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,3 @@ tag.gpgSign::
1515
convenient to use an agent to avoid typing your gpg passphrase
1616
several times. Note that this option doesn't affect tag signing
1717
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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -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].

0 commit comments

Comments
 (0)