Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Andy Koppe <andy.koppe@gmail.com>
Cc: git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [PATCH v2] refs/files: keep root refs out of loose ref cache
Date: Mon, 19 Oct 2026 07:57:10 +0200	[thread overview]
Message-ID: <atWxNvZn3CYTBuFp@pks.im> (raw)
In-Reply-To: <20261017200405.2332914-1-andy.koppe@gmail.com>

On Sat, Oct 17, 2026 at 09:04:00PM +0100, Andy Koppe wrote:
> Changes since v1:
> - Move create_root_ref_cache() below get_loose_ref_cache() for a smaller
>   diff, and tweak its comment.
> - Correct the documentation, help text and refs.h comment for
>   `--include-root-refs`, which claimed that it lists pseudorefs.
> - Consider alternative approaches in the log message.

It would help to also get a range-diff relative to v1 so that a reviewer
can see what exxactly has changed between the two versions.

> diff --git a/Documentation/for-each-ref-options.adoc b/Documentation/for-each-ref-options.adoc
> index 54e2fa95c2..b93ffbd74d 100644
> --- a/Documentation/for-each-ref-options.adoc
> +++ b/Documentation/for-each-ref-options.adoc
> @@ -73,7 +73,8 @@ TAB %(refname)`.
>  	using the same rules as _<pattern>_ above.
>  
>  `--include-root-refs`::
> -	List root refs (`HEAD` and pseudorefs) apart from regular refs.
> +	List root refs such as `HEAD` and `ORIG_HEAD` in addition to regular
> +	refs. (The pseudorefs `FETCH_HEAD` and `MERGE_HEAD` are not included.)
>  
>  `--start-after=<marker>`::
>      Allows paginating the output by skipping references up to and including the

These changes make sense, but they are unrelated to the fix. They should
thus go into a separate commit.

Patrick 

  reply	other threads:[~2026-10-19  5:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 15:32 [PATCH] refs/files: keep root refs out of loose ref cache Andy Koppe
2026-10-15  5:58 ` Patrick Steinhardt
2026-10-15 17:31   ` Junio C Hamano
2026-10-15 19:43     ` Andy Koppe
2026-10-16  7:00       ` Patrick Steinhardt
2026-10-16 15:05         ` Junio C Hamano
2026-10-17 20:04 ` [PATCH v2] " Andy Koppe
2026-10-19  5:57   ` Patrick Steinhardt [this message]
2026-10-19 21:30     ` Andy Koppe
2026-10-19 20:34 ` [PATCH v3] " Andy Koppe
2026-10-20  6:42   ` Patrick Steinhardt

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=atWxNvZn3CYTBuFp@pks.im \
    --to=ps@pks.im \
    --cc=andy.koppe@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.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