From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-rebase.sh: Unchain the git-COMMAND into git COMMAND
Date: Tue, 5 Feb 2008 14:10:40 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0802051407540.8543@racer.site> (raw)
In-Reply-To: <8x1zzemr.fsf@blue.sea.net>
Hi,
On Tue, 5 Feb 2008, Jari Aalto wrote:
> * Mon 2008-02-04 Johannes Schindelin <Johannes.Schindelin@gmx.de>
> * Message-Id: alpine.LSU.1.00.0802042050480.8543@racer.site
> > Hi,
> >
> > On Mon, 4 Feb 2008, Jari Aalto wrote:
> >
> >> -Example: git-rebase master~1 topic
> >> +Example: git rebase master~1 topic
> >
> > From 36e5e70e0f40cf7ca4351b8159d68f8560a2805f(Start deprecating
> > "git-command" in favor of "git command"):
> >
> > (For non-builtins, the "git xyzzy" format implies an extra execve(), so
> > this script leaves those alone).
>
> Please elaborate. I'm not sure I understand. If the git-<command> syntax
> is being phased out, it should be consistent decision accross the tools.
If you call "git xyz", but git-xyz is a script, you will exec the git
wrapper first, which will then exec git-xyz. That is an unnecessary exec.
Since the places you touched are already in a git script (i.e. it was
already called with PATH extended to git's libexec/ directory, if there is
one), we can avoid that extra exec.
The git-<command> syntax _is_ phased out, but in several steps. Let's not
do the third step before the first, otherwise we'll trip.
Ciao,
Dscho
prev parent reply other threads:[~2008-02-05 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 20:25 [PATCH] git-rebase.sh: Unchain the git-COMMAND into git COMMAND Jari Aalto
2008-02-04 20:53 ` Johannes Schindelin
2008-02-05 14:01 ` Jari Aalto
2008-02-05 14:10 ` Johannes Schindelin [this message]
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=alpine.LSU.1.00.0802051407540.8543@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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