ron, i think you misunderstood my intent. i entirely agree that Plan 9 file systems are not VCSs; my point was only that some of the design points overlap. fossil (and kenfs before it, and things like cdfs in other ways) has answered a lot of questions about archival storage; when we see what looks to be a new question in the design of gitfs, it's worth looking at what fossil did, if anything, when faced with a similar problem.
put another way: i wasn't saying "fossil solved this, just use fossil" but rather "fossil solved a similar problem in another context; the solution may apply in this context, as well". i think it's a reasonable line of inquiry, and for the two particular questions posed here (adding files and explicit commit actions), seems to be reasonably informative on at least one of them (adds; Roman's later message may disqualify the commit method). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/plan9-gsoc?hl=en -~----------~----~----~----~------~----~------~--~---
