From: Jeff King <peff@peff.net>
To: "John M. Dlugosz" <ngnr63q02@sneakemail.com>
Cc: git@vger.kernel.org
Subject: Re: File Systems and a Theory of Edits
Date: Sun, 31 Jul 2011 19:22:38 -0600 [thread overview]
Message-ID: <20110801012237.GA32509@sigill.intra.peff.net> (raw)
In-Reply-To: <23101-1312054868-691056@sneakemail.com>
On Sat, Jul 30, 2011 at 02:40:57PM -0500, John M. Dlugosz wrote:
> On 7/30/2011 9:29 AM, Michael Nahas wrote:
> >For these commands to work, the git command will have to include an
> >argument that specifies which commit it operates on. So some basic
> >ones might be:
> > "git ls<commit> -- <path>"
> > "git cat<commit> -- <path>"
> >(There exists "git ls-files", "git ls-tree", and "git cat-file" but
>
> If you could "mount" a repository, then you would not need these
> commands at all. It would be in fact a read-only file system. Once
> mounted, the individual commits could be directories, and under that
> you explore in the usual way.
There are several (mostly fuse-based) tools listed on the wiki:
https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Filesystem_interfaces
I've never used any of them, though. No idea how mature or usable they
are.
Googling around also came up with this newer attempt:
https://github.com/mfontani/git-fuse-perl
Again, no idea on the quality.
-Peff
prev parent reply other threads:[~2011-08-01 1:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 14:29 File Systems and a Theory of Edits Michael Nahas
2011-07-30 19:06 ` Ævar Arnfjörð Bjarmason
2011-07-31 8:15 ` René Scharfe
[not found] ` <CADo4Y9gU_Z73gCPCESvVZhLOJUJg+mTqHkeqpNv2L8xLJvKxEQ@mail.gmail.com>
2011-07-31 14:15 ` Michael Nahas
2011-07-31 17:21 ` Michael Witten
2011-07-31 21:13 ` Michael Nahas
2011-07-31 22:20 ` Andreas Schwab
2011-07-31 22:39 ` Michael Nahas
2011-08-01 12:01 ` Michael Nahas
2011-07-31 16:16 ` René Scharfe
2011-08-01 1:04 ` Junio C Hamano
2011-08-01 11:14 ` Michael Nahas
2011-07-30 19:40 ` John M. Dlugosz
2011-07-31 11:56 ` Michael Witten
2011-08-01 1:22 ` Jeff King [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110801012237.GA32509@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=ngnr63q02@sneakemail.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.
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).