On Sun, Jun 28, 2009 at 5:53 AM, Anthony Sorace<[email protected]> wrote: > > 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?
Git commit is very much akin to fossil's snap. And what is snap? A control message. That's exactly what Manzur's first design is. > commit is trickier, but mostly because of the desire to get commit > messages. Not only that, but also because we would like to record the lineage of commits. Sometimes even with multiple parents. > 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. I don't think you cant get Git semantics that way. Trying to convince the world that you actually don't need Git semantics is really quite counterproductive at this point. Thanks, Roman. P.S. If I'm mistaken and once CAN get Git semantics via FS primitives (and them alone, without resourting to ctl files) I'd be very curious to know how. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
