Keith Packard <keithp@xxxxxxxxxx> wrote: > On Fri, 2007-06-22 at 15:36 +0400, Roman Kagan wrote: > > Wouldn't it be better to teach parsecvs > > to speak git-fast-import language instead? > > Avoiding fork/exec is rather important for parsecvs perforamance. That sort of thing is the entire point behind fast-import. Its only one fork+exec to setup the fast-import "daemon" in the background, and you do everything over a pipe to its stdin. Including forcing it to finish its current packfile and open a new one on the next object (the `checkpoint` command). fast-import is fast, its input language is fairly simple, and its quite stable. And its only one fork+exec. That's peanuts compared to the disk IO involved in any sizable import process. -- Shawn. - 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
