All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #09; Tue, 27)
Date: Fri, 01 Mar 2024 08:21:59 -0800	[thread overview]
Message-ID: <xmqqjzml9b2w.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZQAxGFDrBmq0+Q77YcfT4hBivRu9oOGZF-r81F49P+00Q@mail.gmail.com> (Karthik Nayak's message of "Fri, 1 Mar 2024 02:54:37 -0800")

Karthik Nayak <karthik.188@gmail.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>> * kn/for-all-refs (2024-02-23) 6 commits
>>   (merged to 'next' on 2024-02-27 at aef2406cca)
>>  + for-each-ref: add new option to include root refs
>>  + ref-filter: rename 'FILTER_REFS_ALL' to 'FILTER_REFS_REGULAR'
>>  + refs: introduce `refs_for_each_include_root_refs()`
>>  + refs: extract out `loose_fill_ref_dir_regular_file()`
>>  + refs: introduce `is_pseudoref()` and `is_headref()`
>>  + Merge branch 'ps/reftable-backend' into kn/for-all-refs
>>
>>  "git for-each-ref" filters its output with prefixes given from the
>>  command line, but it did not honor an empty string to mean "pass
>>  everything", which has been corrected.
>>
>>  Will merge to 'master'.
>>  source: <20240223100112.44127-1-karthik.188@gmail.com>
>
> Thanks, the description here needs to be modified since we moved from
> the `an empty string to mean "pass everything"` to providing the
> `--include-root-refs` option.

Good point.  I just updated the draft for the next issue of
'whats-cooking.txt' to read like this:

 "git for-each-ref" learned "--include-root-refs" option to show
 even the stuff outside the 'refs/' hierarchy.

Thanks.

      reply	other threads:[~2024-03-01 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  5:44 What's cooking in git.git (Feb 2024, #09; Tue, 27) Junio C Hamano
2024-02-28 13:38 ` Philippe Blain
2024-02-28 17:25   ` Junio C Hamano
2024-02-29 23:56 ` Linus Arver
2024-03-01  2:02   ` Junio C Hamano
2024-03-01 16:16     ` Junio C Hamano
2024-03-08 19:11       ` Linus Arver
2024-03-01 10:54 ` Karthik Nayak
2024-03-01 16:21   ` Junio C Hamano [this message]

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=xmqqjzml9b2w.fsf@gitster.g \
    --to=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.