From: Karthik Nayak <karthik.188@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #07; Tue, 20)
Date: Wed, 21 Feb 2024 10:04:06 +0100 [thread overview]
Message-ID: <CAOLa=ZQOtDgyWxmV+C9r_wfqo-KdJ5uqW4KwJKD8WdT9qM0t2Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqplwrqbd2.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hello,
Junio C Hamano <gitster@pobox.com> writes:
> * kn/for-all-refs (2024-02-12) 6 commits
> - 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
> (this branch uses ps/reftable-backend.)
>
> "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 'next'?
> source: <20240211183923.131278-1-karthik.188@gmail.com>
Let me know if there's something more I could do here.
Thanks!
- Karthik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]
next prev parent reply other threads:[~2024-02-21 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 17:44 What's cooking in git.git (Feb 2024, #07; Tue, 20) Junio C Hamano
2024-02-21 9:04 ` Karthik Nayak [this message]
2024-02-21 16:44 ` Junio C Hamano
2024-02-22 8:25 ` Patrick Steinhardt
2024-02-22 16:15 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOLa=ZQOtDgyWxmV+C9r_wfqo-KdJ5uqW4KwJKD8WdT9qM0t2Q@mail.gmail.com' \
--to=karthik.188@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).