If you don't mind storing your filesystem in PostgreSQL and accessing it via FUSE, I'm on it. File-by-file and directory-by-directory rollback-and-forward, with branching (roll back and write). A `commit' is done on every open for writing; versioning is done both by filename and by inode number, so editors that write files by unlink()-and-rename() are covered.
(The overhead is necessarily considerable, although access to data at branch tips, which should be most of the accesses is still O(1).)
I'll admit it's mostly for the fun of it... I should have a trac up with design docs and a public svn repo in a week or so (hardware replacement at this end first so I've got the disk space to play with things like this!) and be working on the actual code.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds