Live data from Hacker News

Gitfs

presslabs.com

1–10 of 34 posts

Re: Gitfs

#3
post #2

What is btrfs?

As far as I can see the only difference in this perspective that btrfs can't do merges or rebases. Though for the simple usecase mentioned on the site I think btrfs is well suitable too (website deployment with easy rollbacks).

Re: Gitfs

#4
It's great that git is super fast, but it seems like it would be pretty horrible at handing the binary files that would be needed for actual filesystem applications.

Re: Gitfs

#5
For write support you obviously have to mount a branch. Can you mount tags or commits read-only? It would be really useful actually.

Actually I can't see a use case where I would mount it read-write. For developing a website you possibly do not want to commit on every write. Possibly git's limitations on large files still apply to this implementation. For large number of small files: what does it do when I cp like 1000 files into it? Does it create 1000 commits?

Re: Gitfs

#6
post #5

For write support you obviously have to mount a branch. Can you mount tags or commits read-only? It would be really useful actually. Actually I can't see a use case where I would mount it read-write. For developing a website you possibly do not want to commit on every write. Possibly git's limitations on large files still apply to this implementation. For large number of small files: what does it do when I cp like 10…

> mount -o ro ...

Re: Gitfs

#7
post #5

For write support you obviously have to mount a branch. Can you mount tags or commits read-only? It would be really useful actually. Actually I can't see a use case where I would mount it read-write. For developing a website you possibly do not want to commit on every write. Possibly git's limitations on large files still apply to this implementation. For large number of small files: what does it do when I cp like 10…

[deleted]

Re: Gitfs

#9
There is a nice EuroPython talk were two of the authors talked about gitfs:

https://ep2015.europython.eu/conference/talks/gitfs-building...

Their main motivation to write this was to give their clients (publishers) a way to interact with a git-versioned project tree without having to force them to use git directly. Overall pretty amazing work!

Post reply on HN