From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org, robbat2@gentoo.org, casey@nrlssc.navy.mil,
avarab@gmail.com
Cc: Jon Seymour <jon.seymour@gmail.com>
Subject: [PATCH v5 3/4] rev-parse: update documentation of --flags and --no-flags options
Date: Sun, 26 Sep 2010 02:18:34 +1000 [thread overview]
Message-ID: <1285431515-21321-4-git-send-email-jon.seymour@gmail.com> (raw)
In-Reply-To: <1285431515-21321-1-git-send-email-jon.seymour@gmail.com>
Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
---
Documentation/git-rev-parse.txt | 12 +++++++++++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 341ca90..f5e6637 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -49,10 +49,20 @@ OPTIONS
'git rev-list' command.
--flags::
- Do not output non-flag parameters.
+ Do not output non-flag parameters which are not also revisions.
+ +
+ If specified, this option causes 'git rev-parse' to stop
+ interpreting remaining arguments as options for its own
+ consumption. As such, this option should be specified
+ after all other options that 'git rev-parse' is expected
+ to interpret.
--no-flags::
Do not output flag parameters.
+ +
+ If both `--flags` and `--no-flags` are specified, the first
+ option specified wins and the other option is treated like
+ a non-option argument.
--default <arg>::
If there is no parameter given by the user, use `<arg>`
--
1.7.3.4.g73371.dirty
next prev parent reply other threads:[~2010-09-25 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 16:18 [PATCH v5 0/4] rev-parse: allow --flags to output rev-parse-like flags Jon Seymour
2010-09-25 16:18 ` [PATCH v5 1/4] rev-parse: stop interpreting flags as options to rev-parse once --flags is specified Jon Seymour
2010-09-25 16:18 ` [PATCH v5 2/4] rev-parse: add tests for git rev-parse --flags Jon Seymour
2010-09-25 16:18 ` Jon Seymour [this message]
2010-09-25 16:18 ` [PATCH v5 4/4] rev-parse: make --flags imply --no-revs for remaining arguments Jon Seymour
2010-09-25 16:21 ` Jon Seymour
2010-09-26 1:24 ` [RE: v6 0/4] rev-parse: allow --flags to output rev-parse-like flags Jon Seymour
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=1285431515-21321-4-git-send-email-jon.seymour@gmail.com \
--to=jon.seymour@gmail.com \
--cc=avarab@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=robbat2@gentoo.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;
as well as URLs for NNTP newsgroup(s).