EReru·Sep 19, 2026
On Linux, Fuse is your friend. See eg https://github.com/matthiasgoergens/git-snap-fs
In You can run Git on object storage if you re-make packfilesmatthiasgoergens
git-snap-fs
Rust2025–2026
matthiasgoergens / git-snap-fs
git-snap-fs
Discover this repository through its Hacker News conversations.
2Distinct people
6Mentions
0Explicit recommenders
19GitHub stars
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month6 dated mentions
Observed mentions: 2025-11-10 00:28:32 UTC to 2026-09-19 08:58:03 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 3 | 0 | 3 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
6 sourcesSee https://github.com/matthiasgoergens/git-snap-fs for my example of read-only access to git via fuse.
I built the original version in Python for a job years ago. But the version above is almost entirely vibe-coded in Rust in a lazy afternoon for fun.
However, I disagree that the filesystem is the right abstraction in general. It works for git, because git is essentially structured like a filesystem already.
More generally, filesystems are roughly equivalent to hierarchical databases, or at most graph databases. And while you can make that work, many collections of data are actually better organised and accessed by other means. See https://www.seas.upenn.edu/~zives/03f/cis550/codd.pdf for an particularly interesting and useful model that has found widespread application and success.
In FUSE is All You Need – Giving agents access to anything via filesystemsSee my own https://github.com/matthiasgoergens/git-snap-fs which lets you expose all branches and all tags and all commits and all everything in a git repository as a static directory tree. No need to git checkout anything: everything is already checked out.
In FUSE is All You Need – Giving agents access to anything via filesystemsSee my own https://github.com/matthiasgoergens/git-snap-fs which lets you expose all branches and all tags and all commits and all everything in a git repository as a static directory tree. No need to git checkout anything: everything is already checked out.
In FUSE is All You Need – Giving agents access to anything via filesystemsMount Git repo to view commits and branches as files
6 points · Open discussionI recreated a little tool to simultaneously mount all the commits in a git repository as directories at the same time (but re-use the same inodes for the same content).
The code is at https://github.com/matthiasgoergens/git-snap-fs
The original was in Python and actually had a decent excuse for existing for a very specific problem at work a few years ago. The new version is in Rust and exists just for fun.
This was also a small experiment in coding with OpenAI's codex. I wrote the Python original by hand---like a caveman. Codex was mostly ok at the actual code, especially once I told it to make `cargo clippy` happy, but it needed lots of help with the design. It kept insisting on extra complications and state.
But perhaps I'm a bit unfair here, because I only figured out the nice and simple design after reflecting on the connection be
Read the rest
tween Linux's fuse and git's design for a while when writing the original. So it's only fair that the computer would also need some help to see how to match them up nicely.