On 1 июл, 08:03, Dave Eckhardt <[email protected]> wrote: > > $ 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.
Why not to use diff for that purpose? Diff between index/ and the working directory actually shows what you need. > > 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? Yes, that's more convenient way to view the log. But example with log was supposed to show how file-specific operations are done. There're other file-specific commands that need be executed. Thanks for the idea, I'll definitely use that. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
