Re: VCS comparison table
- From
Petr Baudis <pasky@suse.cz>
- Date
- Oct 17, 2006, 02:40 UTC
- Message-ID
- <20061017024056.GE20017@pasky.or.cz>
- In-Reply-To
- <Pine.LNX.4.63.0610170128350.14200@wbgn013.biozentrum.uni-wuerzburg.de>
Hi!
Dear diary, on Tue, Oct 17, 2006 at 01:45:34AM CEST, I got a letter where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
Show 9 quoted lines
> 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<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)