From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #02; Wed, 8)
Date: Wed, 08 Sep 2021 12:23:57 -0700 [thread overview]
Message-ID: <xmqq8s063m7m.fsf@gitster.g> (raw)
In-Reply-To: <YTjjqV/4/oceM3lM@nand.local> (Taylor Blau's message of "Wed, 8 Sep 2021 12:24:09 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> On Wed, Sep 08, 2021 at 08:38:55AM -0700, Junio C Hamano wrote:
>> * tb/pack-finalize-ordering (2021-09-07) 2 commits
>> - builtin/repack.c: move `.idx` files into place last
>> - pack-write.c: rename `.idx` file into place last
>>
>> The order in which various files that make up a single (conceptual)
>> packfile has been reevaluated and straightened up. This matters in
>> correctness, as an incomplete set of files must not be shown to a
>> running Git.
>>
>> Will merge to 'next'?
>
> Ævar has a series [1] that complements this one nicely, so I would be
> happy to see them both queued.
>
> I had some suggestions inline, but I don't feel strongly about whether
> or not they are implemented.
I hate to see multiple folks "competing" in the overlapping area,
each getting reviews and responding or not responding at their own
pace. That would force me to keep track of which one is which and
what their doneness are independently.
Do you mind if I nominate you the team leader to come up with a
single series that is polished to be mergeable to 'next'?
Thanks.
next prev parent reply other threads:[~2021-09-08 19:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 15:38 What's cooking in git.git (Sep 2021, #02; Wed, 8) Junio C Hamano
2021-09-08 16:24 ` Taylor Blau
2021-09-08 19:23 ` Junio C Hamano [this message]
2021-09-09 1:02 ` Taylor Blau
2021-09-08 21:27 ` Jeff King
2021-09-08 16:55 ` Azeem Bande-Ali
2021-09-08 19:20 ` Junio C Hamano
2021-09-08 17:50 ` Philippe Blain
2021-09-08 21:57 ` Derrick Stolee
2021-09-09 14:23 ` Elijah Newren
2021-09-09 2:59 ` Ramsay Jones
2021-09-09 17:45 ` Junio C Hamano
2021-09-09 11:03 ` js/scalar, was " Johannes Schindelin
2021-09-10 8:52 ` Junio C Hamano
2021-09-09 11:05 ` rs/range-diff-avoid-segfault-with-I, " Johannes Schindelin
2021-09-09 11:08 ` js/retire-preserve-merges, " Johannes Schindelin
2021-09-10 5:00 ` Junio C Hamano
2021-09-09 11:08 ` mr/bisect-in-c-4, " Johannes Schindelin
2021-09-10 5:07 ` Junio C Hamano
2021-09-10 9:33 ` Johannes Schindelin
2021-09-09 11:13 ` lh/systemd-timers, " Johannes Schindelin
2021-09-09 11:15 ` ar/submodule-add-more, " Johannes Schindelin
2021-09-10 5:30 ` Junio C Hamano
2021-09-09 11:18 ` Ævar Arnfjörð Bjarmason
2021-09-09 14:12 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8s063m7m.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).