From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Scott R Parish <srp@srparish.net>
Cc: git@vger.kernel.org, spearce@spearce.org, gitster@pobox.com
Subject: Re: [PATCH] Deduce exec_path also from calls to git with a relative path
Date: Sat, 20 Oct 2007 22:31:47 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710202225520.25221@racer.site> (raw)
In-Reply-To: <1192868006.v2.fusewebmail-240137@f>
Hi,
On Sat, 20 Oct 2007, Scott R Parish wrote:
> Wow, that sure cleaned up nicely! :)
Heh.
BTW I did not mean to discourage you... Rather, I wanted to show you that
this list is a wonderful place to learn, as I did, do, and will do many
times here. (Just to clarify, since somebody said that I am usually not
nice to newbies... cannot understand that at all ;-)
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-21 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 8:13 [PATCH] Deduce exec_path also from calls to git with a relative path Scott R Parish
2007-10-20 21:31 ` Johannes Schindelin [this message]
2007-10-20 23:04 ` Scott Parish
-- strict thread matches above, loose matches on Subject: below --
2007-10-20 6:46 [PATCH] If git is ran with a relative path, try building an absolute exec_path from it Scott R Parish
2007-10-20 7:21 ` [PATCH] Deduce exec_path also from calls to git with a relative path Johannes Schindelin
2007-10-20 12:25 ` David Brown
2007-10-20 21:25 ` Johannes Schindelin
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=Pine.LNX.4.64.0710202225520.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=srp@srparish.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;
as well as URLs for NNTP newsgroup(s).