From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] Add --bool and --int to the OPTIONS section
Date: Wed, 29 Nov 2006 08:25:40 +0000 [thread overview]
Message-ID: <200611290825.40953.andyparkins@gmail.com> (raw)
In-Reply-To: <7vd5772unw.fsf@assigned-by-dhcp.cox.net>
Signed-off-by: Andy Parkins <andyparkins@gmail.com>
---
I did look for just such an option, but didn't find it because it wasn't in
the OPTIONS list of the git-repo-config man page. If there is an OPTIONS
section it should include all options, otherwise it's no use as a quick
reference.
Your template commit message is an excellent idea, but I don't like the idea
of simply hard coding sign off line into it; it means that there are then two
locations in the .git tree that I'd have to edit to change my name.
Therefore any template would have to support token expansion so that "S-o-B:
$REPOSITORY_EMAIL" would be possible. Even better would be support
for "$GIT_STATUS_OUTPUT" and "$GIT_DIFF_OUTPUT" so that the commit message is
completely templated.
Documentation/git-repo-config.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-repo-config.txt
b/Documentation/git-repo-config.txt
index 8199615..5bede9a 100644
--- a/Documentation/git-repo-config.txt
+++ b/Documentation/git-repo-config.txt
@@ -77,6 +77,12 @@ OPTIONS
-l, --list::
List all variables set in config file.
+--bool::
+ git-repo-config will ensure that the output is "true" or "false"
+
+--int::
+ git-repo-config will ensure that the output is a simple decimal number
+
ENVIRONMENT
-----------
--
1.4.3.GIT-dirty
next prev parent reply other threads:[~2006-11-29 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 12:02 [PATCH] Add support for commit.signoff config option Andy Parkins
2006-11-28 20:17 ` Junio C Hamano
2006-11-29 8:25 ` Andy Parkins [this message]
2006-11-29 10:09 ` [PATCH] Add --bool and --int to the OPTIONS section Johannes Schindelin
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=200611290825.40953.andyparkins@gmail.com \
--to=andyparkins@gmail.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.
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).