Hi!
Dear diary, on Tue, Oct 17, 2006 at 01:45:34AM CEST, I got a letter

where Johannes Schindelin  said that...

quoted text
> On Mon, 16 Oct 2006, Aaron Bentley wrote:

> > As the author of two different Arch front-ends, I can say I haven't

> > found that approach satisfactory.  Invoking multiple commands tends

> > re-invoke the same validation routines over and over, killing

> > efficiency, and diagnostics tend to be pretty poorly integrated.

>

> Welcome to git! Git's commands are very efficient, and you can even pipe

> them efficiently! And now that we have GIT_TRACE, diagnostics are no

> concern.

I think Aaron rather meant that in case of an error, the error messages

may seem incoherent from the perspective of a porcelain user if it's

been generated by the plumbing. And I had that problem in Cogito as well

few times in the past, but I think most of those are reasonable now (I

can't think of a counter-example off the top of my head).
Calling multiple git commands _is_ a problem, especially in a loop, but

I think it's more the inherent fork()+execve() overhead than whatever

happens over and over when main() takes over. Many git commands got

adjusted so that you can call them just once and then feed from/to them

over longer time period.
--

				Petr "Pasky" Baudis

Stuff: http://pasky.or.cz/

#!/bin/perl -sp0777i