git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RFC: what should git rev-parse --flags HEAD do?

From
Jon Seymour <jon.seymour@gmail.com>
Date
Sep 25, 2010, 10:11 UTC
Message-ID
<AANLkTimEToibgpUS1KTSruFRdggi3kbAJU5tfk9r6d2U@mail.gmail.com>
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: Junio C Hamano
Message 1 of 4 in “RFC: what should git rev-parse --flags HEAD do?”
  1. Jon SeymourSep 25, 2010
  2. Junio C HamanoSep 25, 2010
  3. Jon SeymourSep 25, 2010
  4. Jon SeymourSep 25, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.