From: Thomas Koch <thomas@koch.ro>
To: Git Mailing List <git@vger.kernel.org>
Subject: git fuse
Date: Thu, 19 Dec 2013 22:15:00 +0100 [thread overview]
Message-ID: <201312192215.01103.thomas@koch.ro> (raw)
Hi,
I'm thinking about using Git for web application deployment and thought that I
wouldn't even need to checkout a worktree if I could access the bare git repo
via fuse.
What would be the performance impact? Once the files are in the filesystem cache
it shouldn't matter anymore, how fast the git fuse layer is, should it?
Do you know any active and stable git-fuse project?
a) https://github.com/davesque/gitfuse
Python, last commit 1 year ago
b) https://github.com/mfontani/git-fuse-perl
Perl, last commit 3 years ago
c)
http://www.seas.upenn.edu/~cse400/CSE400_2008_2009/websites/grant/project.html
http://repo.or.cz/w/figfs.git
thesis, OCaml, last touched in 2009
d) https://github.com/rossbiro/GitFS
Python, recent but declared pre-alpha
e) https://github.com/patrickhaller/git-fs
C, last commit 2 years ago
f) https://github.com/wereHamster/gitfs
https://blog.caurea.org/2009/07/22/having-fun-with-gitfs.html
C, last commit 2 years ago
Regards,
Thomas Koch2
next reply other threads:[~2013-12-19 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 21:15 Thomas Koch [this message]
2013-12-25 23:01 ` git fuse Drew Northup
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=201312192215.01103.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).