From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Sebastian Schuberth" <sschuberth@gmail.com>,
"Raphael Stolt" <raphael.stolt@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 4/4] docs/config: consistify include.path examples
Date: Thu, 11 May 2017 05:14:30 -0400 [thread overview]
Message-ID: <20170511091430.jwpbyca3m32wterq@sigill.intra.peff.net> (raw)
In-Reply-To: <20170511090905.tvkb4bk2ddjzjip4@sigill.intra.peff.net>
Most of the include examples use "foo.inc", but some use
"foo". Since the string of examples are meant to show
variations and how they differ, it's a good idea to change
only one thing at a time. The filename differences are not
relevant to what we're trying to show.
Signed-off-by: Jeff King <peff@peff.net>
---
And yes, I just invented the word consistify. "make X consistent" hides
the meaning at the end, and I couldn't think of a more concise verb.
Prescriptivists beware. :)
Documentation/config.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 70f79ac39..7b08df732 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -172,8 +172,8 @@ Example
[include]
path = /path/to/foo.inc ; include by absolute path
- path = foo ; find "foo" relative to the current file
- path = ~/foo ; find "foo" in your `$HOME` directory
+ path = foo.inc ; find "foo.inc" relative to the current file
+ path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory
; include if $GIT_DIR is /path/to/foo/.git
[includeIf "gitdir:/path/to/foo/.git"]
--
2.13.0.447.g4d26bc97c
next prev parent reply other threads:[~2017-05-11 9:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 17:00 Possible bug in includeIf / conditional includes raphael.stolt
2017-05-10 18:58 ` Sebastian Schuberth
2017-05-10 19:48 ` Ævar Arnfjörð Bjarmason
2017-05-10 21:21 ` Raphael Stolt
2017-05-10 21:37 ` Raphael Stolt
2017-05-11 6:26 ` Jeff King
2017-05-11 6:29 ` Jeff King
2017-05-11 7:19 ` Ævar Arnfjörð Bjarmason
2017-05-11 7:42 ` Jeff King
2017-05-11 7:49 ` Ævar Arnfjörð Bjarmason
2017-05-11 7:54 ` Jeff King
2017-05-11 9:09 ` [PATCH 0/4] doc improvements for config includes Jeff King
2017-05-11 9:10 ` [PATCH 1/4] docs/config: clarify include/includeIf relationship Jeff King
2017-05-11 16:47 ` Ramsay Jones
2017-05-12 9:28 ` Jeff King
2017-05-11 9:11 ` [PATCH 2/4] docs/config: give a relative includeIf example Jeff King
2017-05-11 9:13 ` [PATCH 3/4] docs/config: avoid the term "expand" for includes Jeff King
2017-05-11 9:14 ` Jeff King [this message]
2017-05-11 9:41 ` [PATCH 4/4] docs/config: consistify include.path examples Junio C Hamano
2017-05-11 9:29 ` [PATCH 0/4] doc improvements for config includes Ævar Arnfjörð Bjarmason
2017-05-11 7:54 ` Possible bug in includeIf / conditional includes Junio C Hamano
2017-05-11 7:56 ` Jeff King
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=20170511091430.jwpbyca3m32wterq@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=raphael.stolt@gmail.com \
--cc=sschuberth@gmail.com \
/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).