git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Han-Wen Nienhuys <hanwen@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2021, #02; Thu, 8)
Date: Mon, 12 Apr 2021 13:04:56 +0200	[thread overview]
Message-ID: <CAFQ2z_P=MqT81gLjov6A471Z9sd69qQTep8KG8M8=LO9pJtkpQ@mail.gmail.com> (raw)
In-Reply-To: <CAFQ2z_NQdGfxUSd7kVvWaT-HG_-LSwM_WG+GqJj9fjky0F=ZTg@mail.gmail.com>

On Mon, Apr 12, 2021 at 12:59 PM Han-Wen Nienhuys <hanwen@google.com> wrote:
>> * hn/reftable (2021-03-12) 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.
>>
>>  What's the status of this topic?
>
>

(now without HTML)

I have an update in the pipeline that will address stale files on
Windows, and I can explode the series further. However, it is
fundamentally blocked on someone willing to spend some time reviewing
the series; this seems to be out of my control.

-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--

Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

      parent reply	other threads:[~2021-04-12 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 22:43 What's cooking in git.git (Apr 2021, #02; Thu, 8) Junio C Hamano
2021-04-09  0:15 ` Ævar Arnfjörð Bjarmason
     [not found] ` <CAFQ2z_NQdGfxUSd7kVvWaT-HG_-LSwM_WG+GqJj9fjky0F=ZTg@mail.gmail.com>
2021-04-12 11:04   ` Han-Wen Nienhuys [this message]

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='CAFQ2z_P=MqT81gLjov6A471Z9sd69qQTep8KG8M8=LO9pJtkpQ@mail.gmail.com' \
    --to=hanwen@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).