git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Ori Bernstein <ori@eigenstate.org>
To: Stef Bon <stefbon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: FUSE fs for git.
Date: Wed, 24 Feb 2021 20:40:07 -0800	[thread overview]
Message-ID: <20210224204007.4937ee80121aa1ed553a2d91@eigenstate.org> (raw)
In-Reply-To: <CANXojcx0TOP9SSr1NgXCddQ3PWze-wBLZA5SRO3YhczqO68u0Q@mail.gmail.com>

On Sun, 21 Feb 2021 11:12:19 +0100, Stef Bon <stefbon@gmail.com> wrote:
<snip>
> Now I'm looking it's possible and usefull to add a git fuse fs. The
> thing I ask is:
> 
> - is there an api I can use (lowlevel and/or highlevel or whatever is
> available)?

Not provided as part of git, as far as I'm aware,
but there are other options.

You can probably look at what cgit does to abuse
git internals as an API:

	https://git.zx2c4.com/cgit/tree/cgit.h

It may also make sense to lift code from game
of trees:

	http://gameoftrees.org/

There's also libgit2:

	https://libgit2.org/

> - is it usefull, in other words is there a serious benefit of a git
> filesystem: does it add something?

That seems like a question you'd have to ask yourself.
What would you do with it?

For me: I've got a 9p based git file system as part of
my implementation of git[1].  It's convenient for scripts
on top of git, avoiding scratch files or pipeline wrangling.
But on Unix, git already has much of that implemented.

I also tend to open files from old commits or other branches
to peek at how some code evolved.

[1] http://shithub.us/ori/git9/HEAD/info.html

-- 
    Ori Bernstein

  reply	other threads:[~2021-02-25  4:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 10:12 Stef Bon
2021-02-25  4:40 ` Ori Bernstein [this message]
2021-03-01  7:45   ` Stef Bon
2021-03-01 14:08     ` Ævar Arnfjörð Bjarmason
2021-02-25  5:32 ` Eric Wong

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=20210224204007.4937ee80121aa1ed553a2d91@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=git@vger.kernel.org \
    --cc=stefbon@gmail.com \
    --subject='Re: FUSE fs for git.' \
    /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

Code repositories for project(s) associated with this 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).