From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>,
Brian Gernhardt <brian@gernhardtsoftware.com>,
Brandon Casey <drafnel@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: RFC: what should git rev-parse --flags HEAD do?
Date: Sat, 25 Sep 2010 20:11:19 +1000 [thread overview]
Message-ID: <AANLkTimEToibgpUS1KTSruFRdggi3kbAJU5tfk9r6d2U@mail.gmail.com> (raw)
The documentation for git rev-parse --flags currently states:
Do not output non-flag parameters.
Therefore, one might expect:
$ git rev-parse --flags HEAD
to produce no output.
In fact, it outputs the sha1 hash of HEAD.
Can anyone see a reason why git rev-parse --flags should not be
modified to match the documentation?
If there is agreement that this should change, I can re-roll my
current rev-parse series to include such a change.
jon.
next reply other threads:[~2010-09-25 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 10:11 Jon Seymour [this message]
2010-09-25 17:54 ` RFC: what should git rev-parse --flags HEAD do? Junio C Hamano
2010-09-25 19:38 ` Jon Seymour
2010-09-25 19:46 ` 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=AANLkTimEToibgpUS1KTSruFRdggi3kbAJU5tfk9r6d2U@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=brian@gernhardtsoftware.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).