From: Brian Gernhardt <benji@silverinsanity.com>
To: git@vger.kernel.org
Subject: [PATCH] Document commit.template configuration variable.
Date: Thu, 26 Jul 2007 16:34:59 -0400 [thread overview]
Message-ID: <20070726203459.GA10283@Hermes.local> (raw)
Add it to the list in config.txt and explicitly say that the
--template option to git-commit overrides the configuration variable.
---
d1cc130a5eb50d5bfe1e8b76cab3d8970fd70ad1 added a config var, but
didn't add it to the full list.
Documentation/config.txt | 3 +++
Documentation/git-commit.txt | 5 ++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index dd98d95..3135cb7 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -393,6 +393,9 @@ color.status.<slot>::
or `untracked` (files which are not tracked by git). The values of
these variables may be specified as in color.branch.<slot>.
+commit.template::
+ Specify a file to use as the template for new commit messages.
+
diff.renameLimit::
The number of files to consider when performing the copy/rename
detection; equivalent to the git diff option '-l'.
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 3f36c67..627994e 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -78,9 +78,8 @@ OPTIONS
Use the contents of the given file as the initial version
of the commit message. The editor is invoked and you can
make subsequent changes. If a message is specified using
- the `-m` or `-F` options, this option has no effect. The
- template file may also be specified using the `commit.template`
- configuration variable.
+ the `-m` or `-F` options, this option has no effect. This
+ overrides the `commit.template` configuration variable.
-s|--signoff::
Add Signed-off-by line at the end of the commit message.
--
1.5.3.rc2.38.g11308
reply other threads:[~2007-07-26 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070726203459.GA10283@Hermes.local \
--to=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
/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