From: marius eriksen <marius@monkey.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Gitfiles - fake acme filesystem for Git
Date: Thu, 1 Jan 2015 12:06:49 -0800 [thread overview]
Message-ID: <E6B186ED-9CC4-44F6-AD96-08BECF77EA16@monkey.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Now that there seems to be more git usage in the 9fans community, I figured I’d share a little hack that I’ve been using for a long time. Gitfiles is like Netfiles, but for Git. It’s very useful to browse historical content of Git repositories, especially when inspecting diffs and histories.
It’s at https://github.com/mariusae/gitfiles <https://github.com/mariusae/gitfiles>. A simple ‘mk install’ should do.
From the README:
Gitfiles provides support for browsing Git repositories inside Acme.
It works like, and is based on, Netfiles[1]. Gitfiles presents read-only
access to a fake filesystem of files stored in Git. Gitfiles accepts paths
of the form
/path/to/repo@tree-ish/repository/path
Where /path/to/repo is a valid Git repository, and tree-ish is a valid
tree, commit or tag object name.
I’ve also attached a few screenshots of Gitfiles in action. In the first, I’m just browsing a git log; in the second I’ve B3’d the SHA1 of the third commit; in the third, I’ve B3’d a historical file path from that diff.
Cheers, and enjoy.
-m.
[-- Attachment #2.1: Type: text/html, Size: 2848 bytes --]
[-- Attachment #2.2: Screen Shot 2015-01-01 at 12.00.20 PM.png --]
[-- Type: image/png, Size: 36199 bytes --]
[-- Attachment #2.3: Screen Shot 2015-01-01 at 12.00.30 PM.png --]
[-- Type: image/png, Size: 91163 bytes --]
[-- Attachment #2.4: Screen Shot 2015-01-01 at 12.01.03 PM.png --]
[-- Type: image/png, Size: 78837 bytes --]
next reply other threads:[~2015-01-01 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 20:06 marius eriksen [this message]
2015-01-01 23:40 ` Skip Tavakkolian
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=E6B186ED-9CC4-44F6-AD96-08BECF77EA16@monkey.org \
--to=marius@monkey.org \
--cc=9fans@9fans.net \
/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).