From: "Scott R Parish" <srp@srparish.net>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH trailing ws fixed] use only the PATH for exec'ing gitcommands
Date: Tue, 23 Oct 2007 16:27:42 -0500 (CDT) [thread overview]
Message-ID: <1193174862.v1.fusewebmail-240137@f> (raw)
In-Reply-To: <20071023211202.GA729@steel.home>
> Acked-by: Alex Riesen <raa.lkml@gmail.com>
>
> Don't forget to mention it needs the patch from Johannes re "deducing
> exec_path from calls to git with a relative path" and your
> "current_exec_path"-patch. Took me a while to figure these out...
Sorry about that! I was basing my patches off the head of spearce, as it
sounded like Junio was going to pick that stuff up.
sRp
prev parent reply other threads:[~2007-10-23 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:01 [PATCH] use only the PATH for exec'ing git commands Scott R Parish
2007-10-22 17:44 ` Johannes Schindelin
2007-10-22 19:01 ` Alex Riesen
2007-10-22 19:25 ` Eric Merritt
2007-10-23 4:08 ` [PATCH trailing ws fixed] " Scott Parish
2007-10-23 21:12 ` Alex Riesen
2007-10-23 21:27 ` Scott R Parish [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=1193174862.v1.fusewebmail-240137@f \
--to=srp@srparish.net \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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).