user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: thoughts on Git::Raw / libgit2?
Date: Sat, 19 Sep 2020 09:50:38 +0000	[thread overview]
Message-ID: <20200919095038.GA10832@dcvr> (raw)
In-Reply-To: <20200616214050.GA15110@dcvr>

I noped out of Git::Raw since their manpage explicitly stated
it's an unstable API.  So I'm using Inline::C for libgit2
support (we've been using Inline::C for years, now):

      parent reply	other threads:[~2020-09-19  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 21:40 Eric Wong
2020-06-22 19:24 ` Konstantin Ryabitsev
2020-06-25  4:31   ` Eric Wong
2020-09-19  9:50 ` Eric Wong [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:

  List information:

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

  git send-email \
    --in-reply-to=20200919095038.GA10832@dcvr \ \ \
    --subject='Re: thoughts on Git::Raw / libgit2?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).