for deciding which files to include in archives: fossil has already solved this problem in the 9p/file server world. why not re-use the existing solution? decide whether you want the default for new file creation to be auto-added or not (git and other VCSs tend to not; plan9 file servers tend to), then flip DMTMP where you want the other behavior.
commit is trickier, but mostly because of the desire to get commit messages. otherwise there'd be plenty of good fs-based methods for doing so (cdfs, for example, commits on removal of the directory you've been working in, an operation otherwise non-sensical for WORM things like CDs and VCS systems). i'd suggest focusing on just the unsolved part (commit messages); the quickist hacky method is a reserved file name you must write to before the rm will work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
