Hi Manzur! First of all, let me echo previous posters and say that I'm really impressed with the quality of proposed model. I believe it is a very solid attempt in capturing the essense of what Git does while at the same time mapping it to Plan9 way of doing things.
I would strongly suggest that you expand your examples and reasoning and turn it into a paper once you have reasonable amount of implementation ready. Now for some clarifications. On Tue, Jun 30, 2009 at 2:31 AM, Manzur<[email protected]> wrote: > > Hi All! > > First of all, I want to thank you all for participating in discussion. > > So, last week besides doing what was planned(completing file server > interface with existing library functions), I forked the project, and > created read-only version of gitfs with following layout: > > $ mount {myfs repo} mntpt > > $ cd mntpt > $ ls > drwxrxrx M 4 manzur manzur 314 Jun 25 20:22 master > drwxrxrx M 4 manzur manzur 314 Jun 25 20:22 rdonlygitfs > > Each of the above entry is a branch, and each of them contains > following files: > > tree - snapshot of the file tree when commit was executed. You can > browse it and read files from it. > parent1 - first parent of commit > ... > parentN - Nth parent of commit Are parents files or subdirectories? > Git index will be represented as a directory, so that you can use cp, > rm instead of git add, rm. The same is with stages, each of them is a > directory: > index/ - files that're in stage 0 > index/1 - files that're in stage 1 > index/2 - files that're in stage 2 How does these stages map to Git's show/diff numbers? Thanks, Roman. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
