git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #01; Thu, 2)
Date: Mon, 06 Sep 2021 14:55:10 -0700	[thread overview]
Message-ID: <xmqq4kaxe5dt.fsf@gitster.g> (raw)
In-Reply-To: <CAFQ2z_N8pUsp3cdBpybHBD-V9_1sARCZvSxr0UkMfcwCoQfCbw@mail.gmail.com> (Han-Wen Nienhuys's message of "Mon, 6 Sep 2021 12:36:41 +0200")

Han-Wen Nienhuys <hanwen@google.com> writes:

> On Fri, Sep 3, 2021 at 12:48 AM Junio C Hamano <gitster@pobox.com> wrote:
>> * hn/reftable (2021-08-26) 29 commits
>>  - SQUASH??? https://github.com/git/git/runs/3439941236?check_suite_focus=true#step:5:700
>>  - reftable: fixup for new base topic 3/3
>>  - reftable: fixup for new base topic 2/3
>>  - reftable: fixup for new base topic 1/3
> ..
>>  The "reftable" backend for the refs API.
>
> I posted a subset of these patches as
> https://lore.kernel.org/git/pull.1081.git.git.1630335476.gitgitgadget@gmail.com/

Thanks for a ping.  I saw it but haven't read it.

> As discussed with AEvar, it will probably speed things up if we can
> focus on getting the base library submitted without hooking it up to
> Git. This would avoid cross-interactions with other pending topics,
> and reduce the size of the more controversial topic (hooking it up to
> Git).

My worry is that a "base library" that is not hooked up to anything
that works in the system would not be properly reviewed at all.  Of
course, without review, it would speed things up, but it is unclear
if that the kind of speed we want.

Anyway, I'll eject the old topic and replace them with the latest
one soonish.

Thanks.

  reply	other threads:[~2021-09-06 21:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 22:48 What's cooking in git.git (Sep 2021, #01; Thu, 2) Junio C Hamano
2021-09-03  0:59 ` Philippe Blain
2021-09-03  4:38   ` Junio C Hamano
2021-09-03  2:25 ` Taylor Blau
2021-09-03  4:38   ` Junio C Hamano
2021-09-06  8:55 ` Carlo Arenas
2021-09-06 10:02   ` Ævar Arnfjörð Bjarmason
2021-09-06 21:52     ` Junio C Hamano
2021-09-07 17:39       ` Junio C Hamano
2021-09-06 10:36 ` Han-Wen Nienhuys
2021-09-06 21:55   ` Junio C Hamano [this message]
2021-09-06 22:21     ` Ævar Arnfjörð Bjarmason
2021-09-07 10:13 ` Ævar Arnfjörð Bjarmason
2021-09-07 17:15   ` 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=xmqq4kaxe5dt.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hanwen@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 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 NNTP newsgroup(s).