Why would somebody use such a file system? To make life easier when working with configuration files?
I wish they also described their motive for creating it.
A developer or sys admin would use it to keep track of changes a site owner would do via ftp/sftp. We made it for this specific reason. Track everything! :)
So is this intended as a single user sort of tool? I'm curious how merges, conflicts & branching would interact w/ a tool like this, or whether it's just intended as a way to implement a versioned file system essentially where files can be rolled back to previous states.
Currently it follows a single branch. The merge strategy is to merge with local changes taking priority over remote ones but this can be plugged-in.
Rollbacks can be done by copying from history to current version.
The only thing shaky thing is when there is a force push because local commits will be pushed back.