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 (Dec 2025, #02)
Date: Wed, 10 Dec 2025 08:10:52 +0900 [thread overview]
Message-ID: <xmqqjyyvi743.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZTeEEntiQdCnDd6B8a_ppJrrZqdURhQJV=bNktnp0JqMw@mail.gmail.com> (Karthik Nayak's message of "Tue, 9 Dec 2025 23:46:28 +0100")
Karthik Nayak <karthik.188@gmail.com> writes:
>> * kn/ref-location (2025-12-01) 2 commits
>> - refs: add GIT_REF_URI to specify reference backend and directory
>> - refs: support obtaining ref_store for given dir
>>
>> A mechanism to specify what reference backend to use and store
>> references in which directory is introduced, which would likely to
>> be useful during ref migration.
>>
>> Comments?
>> source: <20251201-kn-alternate-ref-dir-v3-0-c11b946bc2fa@gmail.com>
>
> I'm currently on leave. While I do plan to work on this, my next version
> which is based on Patricks recent review will be a bit delayed.
Understood. Thanks for a note.
>> * kn/fix-fetch-backfill-tag-with-batched-ref-updates (2025-11-21) 3 commits
>> - fetch: fix failed batched updates skipping operations
>> - fetch: fix non-conflicting tags not being committed
>> - fetch: extract out reference committing logic
>>
>> "git fetch" that involves fetching tags, when a tag being fetched
>> needs to overwrite existing one, failed to fetch other tags, which
>> has been corrected.
>>
>> Expecting a (hopefully small and final) reroll.
>> cf. <CAOLa=ZQ-O7V9qHbgeuQ78R1bHGDmGEM6fP5Kr9aC0AfvSF8MZA@mail.gmail.com>
>> source: <20251121-fix-tags-not-fetching-v8-0-23b53a8a8334@gmail.com>
>
> The only change needed from the last review was a typo. I think we should be
> good as is.
Meaning that we prefer to leave the typo in, or just we won't die
with a known typo?
next prev parent reply other threads:[~2025-12-09 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 21:08 What's cooking in git.git (Dec 2025, #02) Junio C Hamano
2025-12-09 22:46 ` Karthik Nayak
2025-12-09 23:10 ` Junio C Hamano [this message]
2025-12-10 10:04 ` Karthik Nayak
2025-12-10 12:00 ` Junio C Hamano
2025-12-12 21:29 ` Karthik Nayak
2025-12-10 7:55 ` Kristoffer Haugsbakk
2025-12-10 9:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqjyyvi743.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 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 NNTP newsgroup(s).