From: Han-Wen Nienhuys <hanwen@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Han-Wen Nienhuys <hanwenn@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [gitgitgadget/git] Reftable support git-core (#539)
Date: Wed, 22 Apr 2020 17:18:40 +0200 [thread overview]
Message-ID: <CAFQ2z_MCG3pD3i3nAJcvQEKytQdHBO8X9ssmeM=pbypghEvwzQ@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2004221327020.46@tvgsbejvaqbjf.bet>
x
On Wed, Apr 22, 2020 at 1:27 PM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> > > Here is the message: <nycvar.QRO.7.76.6.2004101604210.46@tvgsbejvaqbjf.bet>
> > >
> > >
> > Thanks for the reference. I'll look into it.
> >
> > Johannes, if you have specific comments about the reftable patch, please
> > include me (hanwen@google.com) explicitly on your messages.
>
> Sorry, I forgot. Will try to do better next time.
I fixed all the outstanding issues in the last push to GGG. For the
record, the following caused segfaults:
https://github.com/google/reftable/commit/31078a87067ec9c33f496afb6b478eed6e9c3d12
https://github.com/google/reftable/commit/9107ddd6ed73844cb9092dc18ba92091a1132a9e
The message about "bad replace ref name" was a missing copy of the
prefix filter.
The C reftable library was based on the code I wrote in Go first, and
I keep both versions in sync, hence the null/zero initialization of
data throughout.
By now I'm an expert on reftable, but not so much about Git's test
infrastructure, and unfortunately, I lack the time to become an expert
without your guidance, so please give specific feedback.
The most pressing thing right now is that the windows port on GGG says
++ git tag file
fatal: reftable: transaction failure general error
which suggests that renames don't work like I think they do on windows.
> Ciao,
> Dscho
--
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
prev parent reply other threads:[~2020-04-22 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gitgitgadget/git/pull/539@github.com>
[not found] ` <gitgitgadget/git/pull/539/c603037045@github.com>
2020-03-27 11:20 ` [gitgitgadget/git] Reftable support git-core (#539) Han-Wen Nienhuys
[not found] ` <gitgitgadget/git/pull/539/c615547763@github.com>
[not found] ` <CAOw_e7azo1Wb9RO=7kH8kXp4RxTzD6SW4a9w_2ifiGxUmt2YKw@mail.gmail.com>
2020-04-22 11:27 ` Johannes Schindelin
2020-04-22 15:18 ` 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_MCG3pD3i3nAJcvQEKytQdHBO8X9ssmeM=pbypghEvwzQ@mail.gmail.com' \
--to=hanwen@google.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwenn@gmail.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).