All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2026, #05)
Date: Thu, 13 Aug 2026 10:36:39 -0700	[thread overview]
Message-ID: <xmqqv79dsz14.fsf@gitster.g> (raw)
In-Reply-To: <an15Vvcfudlz69TM@pks.im> (Patrick Steinhardt's message of "Thu, 13 Aug 2026 09:59:18 +0200")

Patrick Steinhardt <ps@pks.im> writes:

>> * tb/send-pack-no-ref-delta (2026-07-12) 4 commits
>>  - send-pack: honor `no-ref-delta` capability
>>  - pack-objects: support reuse with `--no-ref-delta`
>>  - pack-objects: introduce `--no-ref-delta`
>>  - t/helper: teach pack-deltas to list delta entries
>> 
>>  'git send-pack' has been taught to refrain from sending 'REF_DELTA'
>>  encoded packfiles when the other side asks it to.
>> 
>>  Needs review.
>>  source: <alQ7WKITYDXfiVn9@com-79390>
>
> In <an0EkMZGEbg6LERc@com-79390> we've agreed that this series can be
> evicted for now in favor of
> <20260807-b4-pks-odb-generate-pack-v1-0-7dec431ae7cd@pks.im>, as Taylor
> still needs some more time to rethink the approach in there.
>
>> * tb/midx-incremental-custom-base (2026-06-12) 3 commits
>>  - midx-write: include packs above custom incremental base
>>  - midx: pass custom '--base' through incremental writes
>>  - t5334: expose shared `nth_line()` helper
>> 
>>  The 'git multi-pack-index write --incremental' command has been
>>  corrected to properly honor the '--base' option.  Previously, the
>>  custom base was ignored by the normal write path; packs from layers
>>  above the selected base were incorrectly skipped by the pack exclusion
>>  logic, and reachability closure for bitmaps was broken.
>> 
>>  Needs review.
>>  source: <cover.1781294771.git.me@ttaylorr.com>
>
> I'll try to have a look at this series later today.

Thanks.

  reply	other threads:[~2026-08-13 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  4:45 What's cooking in git.git (Aug 2026, #05) Junio C Hamano
2026-08-13  7:59 ` Patrick Steinhardt
2026-08-13 17:36   ` Junio C Hamano [this message]
2026-08-13 17:35 ` kh/trailers-no-urls Kristoffer Haugsbakk
2026-08-13 18:33   ` kh/trailers-no-urls 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=xmqqv79dsz14.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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.