git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git <git@vger.kernel.org>,
	Josh Steadmon <steadmon@google.com>
Subject: reftable & jgit compatibility
Date: Wed, 3 Apr 2024 12:36:04 +0200	[thread overview]
Message-ID: <CAOw_e7Z_10b73n91ihsaao_S-XPkNqvY7gTcHvqUODKD-SwPSA@mail.gmail.com> (raw)

Thanks again for taking up this work.

As I'm browsing over your patches (and realizing how much of the
arcana of the format I've forgotten), I hope that I did not make any
errors in implementing the spec (and/or that Shawn didn't deviate his
implementation from the spec). It would be extremely unfortunate if an
incompatibility between CGit and JGit were discovered after it is
released.

So far I have always been able to read JGit reftables using the C / Go
code, but it would be good to systematically test this, ie. generate a
 bunch of tables using JGit and check that passing them through the C
code (read & write) leaves them unchanged. Or perhaps check in some
tables as golden reference data.

Josh can probably connect you to the right folks to help with this on
the JGit side.

-- 
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen


             reply	other threads:[~2024-04-03 10:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 10:36 Han-Wen Nienhuys [this message]
2024-04-03 10:47 ` reftable & jgit compatibility Patrick Steinhardt
2024-04-03 15:57   ` Han-Wen Nienhuys
2024-04-04  6:23     ` Patrick Steinhardt
2024-04-04  6:44       ` Han-Wen Nienhuys
2024-04-04  7:20         ` Patrick Steinhardt
2024-04-04  8:36           ` Han-Wen Nienhuys
2024-04-03 20:54   ` Jeff King
2024-04-04  6:29     ` Patrick Steinhardt
2024-04-03 15:51 ` Luca Milanesio
2024-04-03 16:42   ` 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

  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=CAOw_e7Z_10b73n91ihsaao_S-XPkNqvY7gTcHvqUODKD-SwPSA@mail.gmail.com \
    --to=hanwenn@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=steadmon@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. 
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).