All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #04; Fri, 8)
Date: Tue, 12 Nov 2024 10:07:10 +0900	[thread overview]
Message-ID: <xmqqcyj18dkx.fsf@gitster.g> (raw)
In-Reply-To: <20241111235337.1691851-1-jonathantanmy@google.com> (Jonathan Tan's message of "Mon, 11 Nov 2024 15:53:37 -0800")

Jonathan Tan <jonathantanmy@google.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>> * jt/repack-local-promisor (2024-11-03) 5 commits
>>  - fixup! index-pack: repack local links into promisor packs
>>  - index-pack: repack local links into promisor packs
>>  - t5300: move --window clamp test next to unclamped
>>  - t0410: use from-scratch server
>>  - t0410: make test description clearer
>> 
>>  "git gc" discards any objects that are outside promisor packs that
>>  are referred to by an object in a promisor pack, and we do not
>>  refetch them from the promisor at runtime, resulting an unusable
>>  repository.  Work it around by including these objects in the
>>  referring promisor pack at the receiving end of the fetch.
>> 
>>  Will merge to 'next' when the CI breakage fixup is addressed.
>>  Breaks CI (with a known fix).
>>  source: <cover.1730491845.git.jonathantanmy@google.com>
>
> The fixup in your source tree looks good (verified at
> https://github.com/jonathantanmy/git/actions/runs/11787543288).

Thanks.  Will squashing it in all it takes or does it require more
(like log message updates, perhaps)?

  reply	other threads:[~2024-11-12  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  8:03 What's cooking in git.git (Nov 2024, #04; Fri, 8) Junio C Hamano
2024-11-11 23:53 ` Jonathan Tan
2024-11-12  1:07   ` Junio C Hamano [this message]
2024-11-12  1:19     ` 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=xmqqcyj18dkx.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.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.