All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Luca Milanesio <luca.milanesio@gmail.com>
Cc: git <git@vger.kernel.org>,
	 JGit Developers list <jgit-dev@eclipse.org>,
	Patrick Steinhardt <ps@pks.im>,
	 Josh Steadmon <steadmon@google.com>,
	Han-Wen Nienhuys <hanwenn@gmail.com>
Subject: Re: reftable & jgit compatibility
Date: Wed, 03 Apr 2024 09:42:55 -0700	[thread overview]
Message-ID: <xmqqjzle8kj4.fsf@gitster.g> (raw)
In-Reply-To: <64970945-5E37-4792-9F37-790CFD82A1BF@gmail.com> (Luca Milanesio's message of "Wed, 3 Apr 2024 16:51:04 +0100")

Luca Milanesio <luca.milanesio@gmail.com> writes:

> Hi Han-Wen,
> Thanks for completing the ref-table on JGit and kicking off the work on CGit.
> ...
>> 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.
> ...
> I am happy to experiment the support on GerritHub.io, we have over 40k repositories !

Thanks.

      reply	other threads:[~2024-04-03 16:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 10:36 reftable & jgit compatibility Han-Wen Nienhuys
2024-04-03 10:47 ` 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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqjzle8kj4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hanwenn@gmail.com \
    --cc=jgit-dev@eclipse.org \
    --cc=luca.milanesio@gmail.com \
    --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. 
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.