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

Re: [PATCH v3 3/6] for-each-ref: introduce %(HEAD) asterisk marker

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Nov 16, 2013, 23:23 UTC
Message-ID
<CAPig+cRkaQAZm76tzuPMnddaZE2qaN=yOF8O9dSaB4pzbBq9ww@mail.gmail.com>
In-Reply-To
<1384513148-22633-4-git-send-email-artagnon@gmail.com>

On Fri, Nov 15, 2013 at 5:59 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 28 quoted lines
> 'git branch' shows which branch you are currently on with an '*', but
> 'git for-each-ref' misses this feature.  So, extend its format with
> %(HEAD) for the same effect.
>
> Now you can use the following format in for-each-ref:
>
>   %(HEAD) %(refname:short)
>
> to display an asterisk next to the current ref.
>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
>  Documentation/git-for-each-ref.txt |  4 ++++
>  builtin/for-each-ref.c             | 13 +++++++++++--
>  t/t6300-for-each-ref.sh            |  2 ++
>  3 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
> index f2e08d1..ab3da0e 100644
> --- a/Documentation/git-for-each-ref.txt
> +++ b/Documentation/git-for-each-ref.txt
> @@ -93,6 +93,10 @@ upstream::
>         from the displayed ref. Respects `:short` in the same way as
>         `refname` above.
>
> +HEAD::
> +       Used to indicate the currently checked out branch.  Is '*' if
> +       HEAD points to the current ref, and ' ' otherwise.

"Used to" sounds like it is explaining something it did in the past. None of the other field names are described in this fashion. Perhaps something simpler along the lines of:

    Asterisk "*" if HEAD matches the current ref (the checked out branch),
    otherwise space " ".
> +
>  In addition to the above, for commit and tag objects, the header
>  field names (`tree`, `parent`, `object`, `type`, and `tag`) can
>  be used to specify the value in the header field.
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 6 of 12 in “Replacement for rr/for-each-ref-decoration”
  1. 0/6 Replacement for rr/for-each-ref-decorationRamkumar Ramachandra, Nov 15, 2013
  2. 1/6 t6300 (for-each-ref): clearly demarcate setupRamkumar Ramachandra, Nov 15, 2013
  3. Eric SunshineNov 16, 2013
  4. 2/6 t6300 (for-each-ref): don't hardcode SHA-1 hexesRamkumar Ramachandra, Nov 15, 2013
  5. 3/6 for-each-ref: introduce %(HEAD) asterisk markerRamkumar Ramachandra, Nov 15, 2013
  6. Eric SunshineNov 16, 2013
  7. 4/6 for-each-ref: introduce %(upstream:track[short])Ramkumar Ramachandra, Nov 15, 2013
  8. Eric SunshineNov 16, 2013
  9. Ramkumar RamachandraNov 17, 2013
  10. 5/6 for-each-ref: introduce %(color:...) for colorRamkumar Ramachandra, Nov 15, 2013
  11. Eric SunshineNov 17, 2013
  12. 6/6 for-each-ref: auto reset color after each atomRamkumar Ramachandra, Nov 15, 2013

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.