Re: What's cooking in git.git (Dec 2025, #02)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 9, 2025, 23:10 UTC
- Message-ID
- <xmqqjyyvi743.fsf@gitster.g>
- In-Reply-To
- <CAOLa=ZTeEEntiQdCnDd6B8a_ppJrrZqdURhQJV=bNktnp0JqMw@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 13 quoted lines
>> * 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.
Show 15 quoted lines
>> * 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?