> history is not revision control. One doesn't need to use revision control to keep a reasonable changelog, see for example the /CHANGES file in both Inferno and p9p (obviously revision control can be used to maintain a changelog, whatever that is a good or a bad idea is a matter of argument).
> it works at the filesystem level as a complete > copy of each file is available for each day in the "dump" file > system. thus it works on any file witha granularity of 1 day. > many changes to a file during a day show up as a single > change from day n to day n+1. Actually, fossil works with much more fine grained granularity than one day, it is up to the user to decide how that granularity should be and for how long such snaps should be kept. (sorry for nit picking, you probably knew that already, just was pointing this out for whoever might not know) uriel
