On Fri, Jul 31, 2009 at 11:22, Jakub Narebski<jnareb@xxxxxxxxx> wrote: >> That's my biggest concern. We are actually using a single tree repository >> approach with lot of branches. What led me to Git at first was the ease >> of branching and merging. I used branching and merging with Subversion >> and its painful. > > So it looks like you wouldn't _need_ to split source tree into separate > smaller repositories for performance reasons. Still it might be good > idea to put separate (sub)projects into separate repositories. But > I guess you can do that even at later time (although it would be best > to do this upfront). It looks like they use P4 branches. Which are NOT branches as Git understands it (a line of history). The P4 "branches" are just directories with some metadata regarding recording where the data in the directory were before an act of "branching" (just a server-side recursive copy). In this case (and this must be, as there are no other branches in P4), they'll have to split their repository. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html