From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)
Date: Mon, 21 Dec 2020 10:01:47 -0800 [thread overview]
Message-ID: <xmqqim8vm41g.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAFQ2z_MtpPNSpL9=OoyPfDRfkFxnCO19qBDnY9bnZiEEGtuMsQ@mail.gmail.com> (Han-Wen Nienhuys's message of "Mon, 21 Dec 2020 13:40:03 +0100")
Han-Wen Nienhuys <hanwen@google.com> writes:
> On Sat, Dec 19, 2020 at 6:36 AM Junio C Hamano <gitster@pobox.com> wrote:
>
>> * hn/reftable (2020-12-09) 15 commits
>> . Add "test-tool dump-reftable" command.
>> . git-prompt: prepare for reftable refs backend
>> . Reftable support for git-core
>> . reftable: rest of library
>> . reftable: reftable file level tests
>> . reftable: read reftable files
>> . reftable: write reftable files
>> . reftable: a generic binary tree implementation
>> . reftable: reading/writing blocks
>> . reftable: (de)serialization for the polymorphic record type.
>> . reftable: add blocksource, an abstraction for random access reads
>> . reftable: utility functions
>> . reftable: add error related functionality
>> . reftable: add LICENSE
>> . init-db: set the_repository->hash_algo early on
>>
>> The "reftable" backend for the refs API.
>>
>> Ejected for now, as it has been breaking the tip of 'seen' for too
>> long.
>
>
> Can you provide more information here? The PR at
> https://github.com/git/git/pull/847 passes all tests (except for the
> VSBuild, with errors that seem unrelated.)
Sorry, but it has been a long time that I have no more detail than
the above handy. Older CI history might know more, but I have no
time to dig that right now (and I'd be just as efficient as you
would for doing such things).
I can try including it in one of the today's pushout of 'seen' and
see what breaks, which would be the easiest ;-)
Thanks for pinging.
next prev parent reply other threads:[~2020-12-21 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 5:34 What's cooking in git.git (Dec 2020, #03; Fri, 18) Junio C Hamano
2020-12-19 6:44 ` Eric Sunshine
2020-12-19 17:13 ` Junio C Hamano
2020-12-19 14:10 ` Felipe Contreras
2020-12-19 17:09 ` Junio C Hamano
2020-12-20 2:19 ` Elijah Newren
2020-12-20 7:32 ` Junio C Hamano
2020-12-21 17:25 ` Elijah Newren
2020-12-21 17:50 ` Junio C Hamano
2020-12-21 12:40 ` Han-Wen Nienhuys
2020-12-21 18:01 ` Junio C Hamano [this message]
2020-12-21 19:55 ` [PATCH] SQUASH??? allow t0031 to run with any default branch name Junio C Hamano
2020-12-21 20:19 ` Felipe Contreras
2020-12-22 10:22 ` Han-Wen Nienhuys
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=xmqqim8vm41g.fsf@gitster.c.googlers.com \
--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 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.