Interesting work - and some ideas for the future
Posted Jul 15, 2006 11:23 UTC (Sat) by
nix (subscriber, #2304)
In reply to:
Interesting work - and some ideas for the future by ringerc
Parent article:
The 2006 Linux Filesystems Workshop (Part III)
An avoidance list will be mandatory: probably one global one and one per-directory (non-inherited). We don't want to version vim .swp files, for starters :)
The winnowing idea sounds excellent: I'll incorporate it if I can figure out a user interface! (It sounds like the sort of thing which should be controlled by a minimal cutoff date and some sort of logarithmic or exponential parameter.)
As for the read-only view, well, the current design already has the ability to roll individual files, directories, and trees backwards and forwards in time. It's not stupid at all. :)
Oh, and it's not read-only. If you write to a file (or modify a directory) which is rolled back into the past, you get a branch.
I think I've managed to conform to POSIX everywhere: I'm in the middle of verifying this at the moment. From the point of view of apps which have files open when someone rolls them back, it just looks like someone's done a truncate or a big write... the whole point of this is POSIX conformance with version control layered on top: I don't want to turn out yet *another* versioning system which doesn't support hard links, symlinks, or permissions!
(
Log in to post comments)