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

[PATCH 3/6] doc: git-init: rework definition lists

From
Jean-Noël Avila via GitGitGadget <gitgitgadget@gmail.com>
Date
Mar 10, 2024, 19:10 UTC
Message-ID
<4140c44a34e8c05581de14c2074945d74ecea1d4.1710097830.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.1687.git.1710097830.gitgitgadget@gmail.com>
From: =?UTF-8?q?Jean-No=C3=ABl=20Avila?= <jn.avila@free.fr>

In all cases of option description, each option is in its own term. Use the same format here.

Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
---
 Documentation/git-init.txt | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index e8fe72861dc..5fce39040f2 100644
--- a/Documentation/git-init.txt
+++ b/Documentation/git-init.txt
@@ -99,12 +99,14 @@ The option can have the following values, defaulting to `group` if no value
 is given:
 +
 --
-'umask' (or 'false')::
+umask::
+false::
 
 Use permissions reported by umask(2). The default, when `--shared` is not
 specified.
 
-'group' (or 'true')::
+group::
+true::
 
 Make the repository group-writable, (and g+sx, since the git group may not be
 the primary group of all users). This is used to loosen the permissions of an
@@ -113,11 +115,13 @@ 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')::
+all::
+world::
+everybody::
 
 Same as `group`, but make the repository readable by all users.
 
-'<perm>'::
+<perm>::
 
 _<perm>_ is a 3-digit octal number prefixed with `0` and each file
 will have mode _<perm>_. _<perm>_ will override users'`umask(2)`
-- 
gitgitgadget
Previous: Jean-Noël Avila via GitGitGadgetNext: Jean-Noël Avila via GitGitGadget
Message 4 of 9 in “doc: rework doc files for git-init and git-clone”
  1. 0/6 doc: rework doc files for git-init and git-cloneJean-Noël Avila via GitGitGadget, Mar 10, 2024
  2. 1/6 doc: git-init: format verbatim partsJean-Noël Avila via GitGitGadget, Mar 10, 2024
  3. 2/6 doc: git-init: format placeholdersJean-Noël Avila via GitGitGadget, Mar 10, 2024
  4. 3/6 doc: git-init: rework definition listsJean-Noël Avila via GitGitGadget, Mar 10, 2024
  5. 4/6 doc: git-init: rework config item init.templateDirJean-Noël Avila via GitGitGadget, Mar 10, 2024
  6. 5/6 doc: git-clone: format verbatim wordsJean-Noël Avila via GitGitGadget, Mar 10, 2024
  7. 6/6 doc: git-clone: format placeholdersJean-Noël Avila via GitGitGadget, Mar 10, 2024
  8. Junio C HamanoMar 11, 2024
  9. Jean-Noël AvilaMar 11, 2024

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.