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

[RE: v6 0/4] rev-parse: allow --flags to output rev-parse-like flags

From
Jon Seymour <jon.seymour@gmail.com>
Date
Sep 26, 2010, 01:24 UTC
Message-ID
<AANLkTinuM=TiNC-AhcnNyQdh+AFij4jNU=bBqjJ0HXbC@mail.gmail.com>
In-Reply-To
<1285431515-21321-1-git-send-email-jon.seymour@gmail.com>

Those interested in the latest version of this series can poll the stop-interpreting-after-flags branch on git://github.com/jonseymour/git.git

I have tagged v6 which is re-organized slightly w.r.t v5 so that tests and documentation of existing behaviour are cleanly separated from proposed changes.

I will post another version of this series to the list if/when I receive additional feedback or a final ack.

Regards,
jon seymour.
Previous: Jon Seymour
Message 7 of 7 in “rev-parse: allow --flags to output rev-parse-like flags”
  1. 0/4 rev-parse: allow --flags to output rev-parse-like flagsJon Seymour, Sep 25, 2010
  2. 1/4 rev-parse: stop interpreting flags as options to rev-parse once --flags is specifiedJon Seymour, Sep 25, 2010
  3. 2/4 rev-parse: add tests for git rev-parse --flags.Jon Seymour, Sep 25, 2010
  4. 3/4 rev-parse: update documentation of --flags and --no-flags optionsJon Seymour, Sep 25, 2010
  5. 4/4 rev-parse: make --flags imply --no-revs for remaining arguments.Jon Seymour, Sep 25, 2010
  6. Jon SeymourSep 25, 2010
  7. 0/4 rev-parse: allow --flags to output rev-parse-like flagsJon Seymour, Sep 26, 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.