From: Chris Angelico <rosuav@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Kevin <ikke@ikke.info>, git <git@vger.kernel.org>
Subject: Re: Configuring a third-party git hook
Date: Fri, 21 Mar 2014 15:07:08 +1100 [thread overview]
Message-ID: <CAPTjJmqRFbKxe8MODtBDDC0SUYGoaFmQj2724YmKnMmdbrgOUA@mail.gmail.com> (raw)
In-Reply-To: <20140321034334.GA29683@sigill.intra.peff.net>
On Fri, Mar 21, 2014 at 2:43 PM, Jeff King <peff@peff.net> wrote:
> Thanks, the new text looks good to me. Please follow SubmittingPatches
> (notably, you need to sign-off your work, and please send patches inline
> rather than as attachments).
Ah, didn't see that file.
>From 6e1fc126ece37c6201d0c16b76c6c87781f7b02b Mon Sep 17 00:00:00 2001
From: Chris Angelico <rosuav@gmail.com>
Date: Fri, 21 Mar 2014 10:45:08 +1100
Subject: [PATCH] Explain that third-party tools may create 'git config'
variables
Signed-off-by: Chris Angelico <rosuav@gmail.com>
---
Documentation/config.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 73c8973..23f0466 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -131,8 +131,9 @@ Variables
Note that this list is non-comprehensive and not necessarily complete.
For command-specific variables, you will find a more detailed description
-in the appropriate manual page. You will find a description of non-core
-porcelain configuration variables in the respective porcelain documentation.
+in the appropriate manual page. Other git-related tools may define their own
+variables, which will be defined on their respective manual pages; ideally,
+these will be named in some way to indicate the project or creator.
advice.*::
These variables control various optional help messages designed to
--
1.7.10.4
Made that patch off master, which is currently basically the same as
maint anyway.
ChrisA
next prev parent reply other threads:[~2014-03-21 4:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 11:16 Configuring a third-party git hook Chris Angelico
2014-03-20 12:53 ` Kevin
2014-03-20 16:51 ` Chris Angelico
2014-03-20 23:38 ` Jeff King
2014-03-20 23:46 ` Chris Angelico
2014-03-21 3:43 ` Jeff King
2014-03-21 4:07 ` Chris Angelico [this message]
2014-03-21 17:31 ` Junio C Hamano
2014-03-21 17:48 ` Chris Angelico
2014-03-21 18:15 ` Jeff King
2014-03-21 18:53 ` Junio C Hamano
2014-03-21 18:54 ` Junio C Hamano
2014-03-20 16:53 ` Junio C Hamano
2014-03-20 17:10 ` Chris Angelico
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPTjJmqRFbKxe8MODtBDDC0SUYGoaFmQj2724YmKnMmdbrgOUA@mail.gmail.com \
--to=rosuav@gmail.com \
--cc=git@vger.kernel.org \
--cc=ikke@ikke.info \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).