From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Marco Costalba <mcostalba@yahoo.it>, junkio@cox.net, git@vger.kernel.org
Subject: Re: git --exec-path conversion
Date: Sat, 19 Nov 2005 04:05:12 -0800 [thread overview]
Message-ID: <7vu0e86dxj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0511191218370.27986@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Sat, 19 Nov 2005 12:20:26 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Little nit: Test for "git-", because "git" and "gitk" will stay in the
> PATH.
Heh, he is writing QGit; why should he run gitk ;-)?
next prev parent reply other threads:[~2005-11-19 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 11:14 git --exec-path conversion Marco Costalba
2005-11-19 11:20 ` Johannes Schindelin
2005-11-19 12:05 ` Junio C Hamano [this message]
2005-11-19 12:04 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-11-19 11:32 Marco Costalba
2005-11-19 13:51 ` Johannes Schindelin
2005-11-19 13:50 Marco Costalba
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=7vu0e86dxj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
/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;
as well as URLs for NNTP newsgroup(s).