> $ git checkout branch > #...some editing... > $ git add file1 > $ git commit -m "msg" > > will be changed to > > $ cd branch/tree > #..some editing... > $ cp file1 /mnt/index/ > $ cp commit_msg /mnt/index > $ mv /mnt/index COMMIT
This shows promise. I think there are a couple more steps floating around somewhere, though: a user needs to know or recall or determine *which* files need to be added. My proposal for a "status" file was to have the SCM present that information to the user. > Each file under some branch will have two modes: command > and textual. Modes are changed by chgrping to the special > value. By default, it's in textual mode. > > #we should change to command mode > $ chgrp MAGIC file1 > $ echo log > file1 > $ cat file1 > #Log for the file1 I think this will turn out to be painful in practice. How about presenting the log for foo.c as log/foo.c? Dave Eckhardt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
