From: Han-Wen Nienhuys <hanwen@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: reftable (was: Re: none)
Date: Fri, 22 Nov 2019 02:38:25 -0800 [thread overview]
Message-ID: <CAFQ2z_PbPEH3=9uJHqXdjV+pxF_-NSS2PGY1ZU-JtxRAuxN66g@mail.gmail.com> (raw)
In-Reply-To: <xmqqsgmjb13r.fsf@gitster-ct.c.googlers.com>
On Tue, Nov 19, 2019 at 8:53 PM Junio C Hamano <gitster@pobox.com> wrote:
> > I spent the last few weeks cobbling together an implementation of the
> > reftable format in C and in Go. I thought this would be cool to add to
> > git-core, but I doubt whether I will have enough time to see such an
> > effort through. Maybe some of you would want to try integrating it
> > into the Git-core code base? Example code is here:
> >
> > https://github.com/google/reftable/blob/master/c/api.h#L153
> >
> > cheers!
>
> My initial impression was that the API overuses typedef.
I changed the code to use struct throughout.
> But the set of operations defined in the header file seemed at the
> right granularity in order to interface with the refs.h & refs/* API
> we have. It however was unclear to me how transactional ref updates
> would work with it.
I implemented the reftable stack in Go, see
https://godoc.org/github.com/google/reftable#Stack
which I could implement in C too. Would that work?
--
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
next prev parent reply other threads:[~2019-11-22 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 3:49 Han-Wen Nienhuys
2019-11-20 4:52 ` none Junio C Hamano
2019-11-20 5:00 ` none Han-Wen Nienhuys
2019-11-22 10:38 ` Han-Wen Nienhuys [this message]
2019-11-20 5:30 ` your mail Taylor Blau
2019-11-20 8:05 ` Christian Couder
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_PbPEH3=9uJHqXdjV+pxF_-NSS2PGY1ZU-JtxRAuxN66g@mail.gmail.com' \
--to=hanwen@google.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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).