Just wondering. A simple git frontend could do that pretty well - just strip it down to message-free one file commits.
That enables you to display the history of a file by handling the output of <git log $file> without confusing the user too much (it's linear, just like his changes), you get full reverts, syncing (push if you have internet), multi-device-support (clone). You'd even be independent from the actual repository host with the app itself, since git doesn't care about it's remote location.
It sounds like a pretty good idea just from thinking about it for a minute.
That enables you to display the history of a file by handling the output of <git log $file> without confusing the user too much (it's linear, just like his changes), you get full reverts, syncing (push if you have internet), multi-device-support (clone). You'd even be independent from the actual repository host with the app itself, since git doesn't care about it's remote location.
It sounds like a pretty good idea just from thinking about it for a minute.