git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Stef Bon <stefbon@gmail.com>
Cc: Bryan Turner <bturner@atlassian.com>, Git Users <git@vger.kernel.org>
Subject: Re: Possible to use git over custom ssh libraries?
Date: Fri, 5 Mar 2021 21:53:46 +0000	[thread overview]
Message-ID: <YEKoav/IOp4Mpe4H@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CANXojcymWsK4g7s5rx0_OPu_XSf4ZiKUbYgQ-h38cvF5WYQs=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On 2021-03-05 at 14:22:42, Stef Bon wrote:
> Hi Bryan,
> 
> thanks for your reaction. Git itself can thus deal with a different
> ssh implementation, only I cannot use that for
> my fuse fs. I need I library which "talks" git.
> 
> What is libgit2 in this context? Is it a library which uses the git
> internals, or is git self written in libgit2?
> And can I use that to use custom ssh libraries and build a fuse fs with it?

libgit2 is an independent implementation of Git as a library.  Git and
libgit2 generally don't share code, although some code has been copied
from one to the other.  It supports SSH using libssh2, although you
could probably patch it to use a different library.

That's the only general purpose C-compatible implementation of Git as a
library that I'm aware of.
-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2021-03-05 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  8:13 Possible to use git over custom ssh libraries? Stef Bon
2021-03-05  8:30 ` Bryan Turner
2021-03-05 14:22   ` Stef Bon
2021-03-05 21:53     ` brian m. carlson [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=YEKoav/IOp4Mpe4H@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=stefbon@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).