From: second.payre@gmail.com
To: git@vger.kernel.org
Cc: PAYRE NATHAN p1508475 <nathan.payre@etu.univ-lyon1.fr>,
MOY Matthieu <matthieu.moy@univ-lyon1.fr>,
Daniel Bensoussan <daniel.bensoussan--bohm@etu.univ-lyon1.fr>,
Timothee Albertin <timothee.albertin@etu.univ-lyon1.fr>,
Nathan Payre <second.payre@gmail.com>
Subject: [PATCH v2] Documentation/git-config.txt: reword missleading sentence
Date: Thu, 12 Oct 2017 11:17:27 +0200 [thread overview]
Message-ID: <20171012091727.30759-1-second.payre@gmail.com> (raw)
In-Reply-To: <xmqqtvz7pewn.fsf@gitster.mtv.corp.google.com>
From: PAYRE NATHAN p1508475 <nathan.payre@etu.univ-lyon1.fr>
Change the word "bla" to "section.variable", "bla" is a placeholder
for a variable name and it wasn't clear for everyone.
This change clarify it.
Change the appearance of 'git config section.variable {tilde}/' to
`git config section.variable {tilde}/` to harmonize it with
the rest of the file, this is a command line then the "`" are
necessary.
Replace "git-config" by "git config" because the command
is not "git-config".
See discussion at:
https://public-inbox.org/git/20171002061303.Horde.SL92grZCqTRV9oQkBFPELQ7@crashcourse.ca/
Signed-off-by: MOY Matthieu <matthieu.moy@univ-lyon1.fr>
Signed-off-by: Daniel Bensoussan <daniel.bensoussan--bohm@etu.univ-lyon1.fr>
Signed-off-by: Timothee Albertin <timothee.albertin@etu.univ-lyon1.fr>
Signed-off-by: Nathan Payre <second.payre@gmail.com>
Noticed-by: rpjday@crashcourse.ca
---
Documentation/git-config.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt
index 83f86b923..2ab9e4c56 100644
--- a/Documentation/git-config.txt
+++ b/Documentation/git-config.txt
@@ -174,11 +174,11 @@ See also <<FILES>>.
either --bool or --int, as described above.
--path::
- 'git-config' will expand leading '{tilde}' to the value of
+ 'git config' will expand leading '{tilde}' to the value of
'$HOME', and '{tilde}user' to the home directory for the
specified user. This option has no effect when setting the
- value (but you can use 'git config bla {tilde}/' from the
- command line to let your shell do the expansion).
+ value (but you can use `git config section.variable {tilde}/`
+ from the command line to let your shell do the expansion).
-z::
--null::
--
2.14.2
next prev parent reply other threads:[~2017-10-12 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 8:17 [PATCH] Documentation/git-config.txt: reword missleading sentence PAYRE NATHAN p1508475
2017-10-05 10:13 ` Junio C Hamano
2017-10-10 8:19 ` Nathan PAYRE
2017-10-10 8:48 ` Junio C Hamano
2017-10-12 9:17 ` second.payre [this message]
2017-10-13 0:23 ` [PATCH v2] " Junio C Hamano
2017-10-13 8:32 ` Moy Matthieu
2017-10-13 12:04 ` Junio C Hamano
2017-10-18 20:27 ` [PATCH v3] " PAYRE NATHAN p1508475
2017-10-18 22:12 ` Jonathan Nieder
2017-10-19 4:58 ` Junio C Hamano
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=20171012091727.30759-1-second.payre@gmail.com \
--to=second.payre@gmail.com \
--cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
--cc=git@vger.kernel.org \
--cc=matthieu.moy@univ-lyon1.fr \
--cc=nathan.payre@etu.univ-lyon1.fr \
--cc=timothee.albertin@etu.univ-lyon1.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).