From: Mitchell Blank Jr <mitch@sfgoth.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] gitfs pre-release 0.02
Date: Tue, 4 Oct 2005 03:51:54 -0700 [thread overview]
Message-ID: <20051004105154.GH32664@gaz.sfgoth.com> (raw)
When I announced the first pre-release of my little gitfs tool back in
June[1] I didn't get much response. (Actually, that's not quite true -- I
got zero response :-) I've been very busy and haven't had the chance to
implement any of the big missing functionality yet, nor will I have time
for at least awhile. Hopefully I'll have some time over the holidays to
hack on it.
However, two things HAVE changed:
1. FUSE is now in the latest mainline kernels, so the barrier-to-entry for
toying with it is lower now
2. The introduction of git packs a couple months ago broke it; this is now
fixed
Other than rebasing against git-core-0.99.8 the only major changes are:
* now runs in non-debugging mode by default (use '-d' to enable debugging
mode)
* some efficiency improvements in the directory-handling code
All the limitations and caveats in the original announcement still apply.
As always -- http://www.sfgoth.com/~mitch/linux/gitfs/
-Mitch
[1] -- http://marc.theaimsgroup.com/?l=git&m=111975978111303&w=2
reply other threads:[~2005-10-04 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051004105154.GH32664@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--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