git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/7] Documentation: git-init: list items facelift

From
Linus Arver <linusarver@gmail.com>
Date
Aug 2, 2014, 18:06 UTC
Message-ID
<1407002817-29221-3-git-send-email-linusarver@gmail.com>
In-Reply-To
<1407002817-29221-1-git-send-email-linusarver@gmail.com>
No textual change.
Signed-off-by: Linus Arver <linusarver@gmail.com>
---
 Documentation/git-init.txt | 49 ++++++++++++++++++++++++++--------------------
 1 file changed, 28 insertions(+), 21 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 5ed5859..45501d0 100644
--- a/Documentation/git-init.txt
+++ b/Documentation/git-init.txt
@@ -72,30 +72,37 @@ repository.  When specified, the config variable "core.sharedRepository" is
 set so that files and directories under `$GIT_DIR` are created with the
 requested permissions.  When not specified, Git will use permissions reported
 by umask(2).
-
++
 The option can have the following values, defaulting to 'group' if no value
 is given:
++
+--
+'umask' (or 'false')::
+
+Use permissions reported by umask(2). The default, when `--shared` is not
+specified.
+
+'group' (or 'true')::
 
- - 'umask' (or 'false'): Use permissions reported by umask(2). The default,
-   when `--shared` is not specified.
-
- - 'group' (or 'true'): Make the repository group-writable, (and g+sx, since
-   the git group may be not the primary group of all users).
-   This is used to loosen the permissions of an otherwise safe umask(2) value.
-   Note that the umask still applies to the other permission bits (e.g. if
-   umask is '0022', using 'group' will not remove read privileges from other
-   (non-group) users). See '0xxx' for how to exactly specify the repository
-   permissions.
-
- - 'all' (or 'world' or 'everybody'): Same as 'group', but make the repository
-   readable by all users.
-
- - '0xxx': '0xxx' is an octal number and each file will have mode '0xxx'.
-   '0xxx' will override users' umask(2) value (and not only loosen permissions
-   as 'group' and 'all' does). '0640' will create a repository which is
-   group-readable, but not group-writable or accessible to others. '0660' will
-   create a repo that is readable and writable to the current user and group,
-   but inaccessible to others.
+Make the repository group-writable, (and g+sx, since the git group may be not
+the primary group of all users). This is used to loosen the permissions of an
+otherwise safe umask(2) value. Note that the umask still applies to the other
+permission bits (e.g. if umask is '0022', using 'group' will not remove read
+privileges from other (non-group) users). See '0xxx' for how to exactly specify
+the repository permissions.
+
+'all' (or 'world' or 'everybody')::
+
+Same as 'group', but make the repository readable by all users.
+
+'0xxx'::
+
+'0xxx' is an octal number and each file will have mode '0xxx'. '0xxx' will
+override users' umask(2) value (and not only loosen permissions as 'group' and
+'all' does). '0640' will create a repository which is group-readable, but not
+group-writable or accessible to others. '0660' will create a repo that is
+readable and writable to the current user and group, but inaccessible to others.
+--
 
 By default, the configuration flag 'receive.denyNonFastForwards' is enabled
 in shared repositories, so that you cannot force a non fast-forwarding push
-- 
2.0.3
Previous: Linus ArverNext: Linus Arver
Message 5 of 30 in “lots of documentation fixes/rewordings in git-init(1)”
  1. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 2, 2014
  2. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 2, 2014
  3. Junio C HamanoAug 5, 2014
  4. Linus ArverAug 6, 2014
  5. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 2, 2014
  6. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 2, 2014
  7. Junio C HamanoAug 5, 2014
  8. Linus ArverAug 6, 2014
  9. Junio C HamanoAug 6, 2014
  10. Linus ArverAug 8, 2014
  11. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 2, 2014
  12. Junio C HamanoAug 5, 2014
  13. Linus ArverAug 6, 2014
  14. Junio C HamanoAug 6, 2014
  15. Linus ArverAug 8, 2014
  16. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 2, 2014
  17. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 2, 2014
  18. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 2, 2014
  19. Junio C HamanoAug 5, 2014
  20. Linus ArverAug 6, 2014
  21. Junio C HamanoAug 6, 2014
  22. Linus ArverAug 8, 2014
  23. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 8, 2014
  24. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 8, 2014
  25. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 8, 2014
  26. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 8, 2014
  27. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 8, 2014
  28. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 8, 2014
  29. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 8, 2014
  30. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 8, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.