On Thu, Jan 29, 2009 at 1:09 PM, Roman V. Shaposhnik <r...@sun.com> wrote: > "trees" tend to be highly overloaded, but if you refer > to the filesystem hierarchy as seem by open, then the > above statement, if applied to Git, is misleading.
What I mean is that if there is some file in the "repository" and I have a long-standing change to it (perhaps I have edited a template config file), the revision control systems tend to get annoyed that you're not checking that change back in. Mercurial, for instance, requires you to say -f on hg merge if you have pending changes. And I think that might even have disappeared in a recent version: you just can't merge anymore in an "unclean" repository. I am not talking about trees as trees of revision history; I just meant the local file system. I don't know how well Git handles this; I apologize for that. I think using venti as a backend for Git would buy you very little. Git already does a good job of managing its blocks. Russ
