> > But suppose we even bite the bullet and > have all the junk managed by gitfs. What's > the FS action to correspond to: > $ git add file1 file2 file3 > $ git commit -m"Change #1" > ? > You would touch file1, file2, file3, rm file4
and compile and all you like. (Using ram storage for temporary files, or a local temporary tree if you like). Then, after mk clean if you don't want binaries, you'd go to /mnt/trees/ and say mv <sha1> clone (clone would commit and then rename sh1 to the right name). Regarding the comment for commit, you can have a fake /mnt/trees/<sha1.README> or whatever so that you could edit it, write whatever you have to say, and then commit would use that as the comment. In fact I'd not use shaN as the names. I mean, you could cd into that if that's waht you know but I think I'd make the name a name. Not too git, but more friendly. It's easy to keep an index so the user could echo sha myname >>index An alternative I'm thinking about is this: cd /mnt/trees sha1 there is considered read only Then you decide to work on sha1 and do a mv sha1 your-symbolic-name you add, remove, edit files. you could handle commit as I said above. In any case, these are just ideas. I hope it might help to make it more close to an actual FS than it would be having to issue multiple ctls. In particular, I see more natural editing a COMMENTS or README file to tag commited trees than to use a ctl, and being able to use the tree as seem instead of having to remember which files to add, remove etc. If you want to git status, you could have a /mnt/tree/name/STATUS file that you could cat. And so on. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
