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 (Oct 2026, #10)
Date: Thu, 29 Oct 2026 11:17:42 -0700	[thread overview]
Message-ID: <xmqqfqxo2wxl.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZSKqRU0okvmvazTieLFKJKZPAxF=1fsVFa7mQhkAz4iLA@mail.gmail.com> (Karthik Nayak's message of "Thu, 29 Oct 2026 05:46:45 -0700")

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

> Junio C Hamano <gitster@pobox.com> writes:
>
>> * kn/fetch-tag-backfill-batch-fix (2026-10-28) 3 commits
>>  - t5510: cover upstream info update on fetch failure
>>  - fetch: advertise fetched refs when backfilling tags
>>  - transport: add `transport_options_release()`
>>
>>  The tag backfilling negotiation in 'git fetch' has been updated to
>>  explicitly include the in-flight fetched tips as 'haves', preventing
>>  the server from resending objects when batched reference updates are
>>  used.
>>
>>  Will merge to 'next'?
>>  cf. <auHfmzP3aXyonp3C@pks.im>
>>  source: <20261028-799-shallow-fetch-with-tags-v5-0-7c43cc9ae810@gmail.com>
>>
>
> I've sent in a v6 with minute fixes, that version should be good to
> merge to 'next'. Thanks

Replaced.  Thanks.

      reply	other threads:[~2026-10-29 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  3:07 What's cooking in git.git (Oct 2026, #10) Junio C Hamano
2026-10-29  8:38 ` Harald Nordgren
2026-10-29 14:29   ` Junio C Hamano
2026-10-29 12:37 ` Patrick Steinhardt
2026-10-29 22:22   ` Junio C Hamano
2026-10-29 12:46 ` Karthik Nayak
2026-10-29 18:17   ` 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=xmqqfqxo2wxl.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.