From: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Jean-Noël Avila" <jn.avila@free.fr>,
"Jean-Noël Avila" <jn.avila@free.fr>
Subject: [PATCH 3/6] doc: git-init: rework definition lists
Date: Sun, 10 Mar 2024 19:10:27 +0000 [thread overview]
Message-ID: <4140c44a34e8c05581de14c2074945d74ecea1d4.1710097830.git.gitgitgadget@gmail.com> (raw)
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
next prev parent reply other threads:[~2024-03-10 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 19:10 [PATCH 0/6] doc: rework doc files for git-init and git-clone Jean-Noël Avila via GitGitGadget
2024-03-10 19:10 ` [PATCH 1/6] doc: git-init: format verbatim parts Jean-Noël Avila via GitGitGadget
2024-03-10 19:10 ` [PATCH 2/6] doc: git-init: format placeholders Jean-Noël Avila via GitGitGadget
2024-03-10 19:10 ` Jean-Noël Avila via GitGitGadget [this message]
2024-03-10 19:10 ` [PATCH 4/6] doc: git-init: rework config item init.templateDir Jean-Noël Avila via GitGitGadget
2024-03-10 19:10 ` [PATCH 5/6] doc: git-clone: format verbatim words Jean-Noël Avila via GitGitGadget
2024-03-10 19:10 ` [PATCH 6/6] doc: git-clone: format placeholders Jean-Noël Avila via GitGitGadget
2024-03-11 17:05 ` Junio C Hamano
2024-03-11 21:43 ` Jean-Noël Avila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4140c44a34e8c05581de14c2074945d74ecea1d4.1710097830.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).