From: Petr Baudis <pasky@suse•cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Matthias Lederhofer <matled@gmx•net>,
Junio C Hamano <junkio@cox•net>,
git@vger•kernel.org
Subject: Re: [PATCH] GIT_TRACE: show which built-in/external commands are executed
Date: Sun, 25 Jun 2006 16:22:03 +0200 [thread overview]
Message-ID: <20060625142203.GF21864@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0606251607090.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
Dear diary, on Sun, Jun 25, 2006 at 04:11:48PM CEST, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx•de> said that...
> P.S.: Now we only have to convert all "git-" invocations in the scripts to
> "git " invocations so we can benefit from it. But that would mean two
> forks instead of one for the non-builtins. Hmm.
actually this is a myth - not two fork()s since 'git' has no reason to
fork; only two execve()s in line after a single fork().
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.
next prev parent reply other threads:[~2006-06-25 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 10:57 [RFC] git --trace: trace command execution Matthias Lederhofer
2006-06-25 11:50 ` Junio C Hamano
2006-06-25 12:51 ` Matthias Lederhofer
2006-06-25 13:56 ` [PATCH] GIT_TRACE: show which built-in/external commands are executed Matthias Lederhofer
2006-06-25 14:11 ` Johannes Schindelin
2006-06-25 14:22 ` Petr Baudis [this message]
2006-06-25 16:10 ` Matthias Lederhofer
2006-06-25 23:30 ` Johannes Schindelin
2006-06-28 18:22 ` Matthias Lederhofer
2006-06-29 18:06 ` [RFC] git --trace: trace command execution Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060625142203.GF21864@pasky.or.cz \
--to=pasky@suse$(echo .)cz \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=matled@gmx$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox