From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] run-command: fix Unix PATH lookup
Date: Wed, 24 Oct 2018 03:36:37 -0400 [thread overview]
Message-ID: <20181024073637.GA31069@sigill.intra.peff.net> (raw)
This series fixes a bug where run-command.c accidentally runs commands
from the current directory when they are not found in the $PATH.
The second patch is the interesting one. The first one is just a
necessary cleanup. Possibly this should be split into two topics: the
second patch slated for maint, and then the first one as an independent
fixup on tb/filter-alternate-refs (which is in master).
[1/2]: t5410: use longer path for sample script
[2/2]: run-command: mark path lookup errors with ENOENT
run-command.c | 20 ++++++++++++++++----
t/t0061-run-command.sh | 13 ++++++++++++-
t/t5410-receive-pack-alternates.sh | 2 +-
3 files changed, 29 insertions(+), 6 deletions(-)
-Peff
next reply other threads:[~2018-10-24 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 7:36 Jeff King [this message]
2018-10-24 7:37 ` [PATCH 1/2] t5410: use longer path for sample script Jeff King
2018-10-24 8:53 ` Johannes Schindelin
2018-10-25 1:15 ` Junio C Hamano
2018-10-24 7:38 ` [PATCH 2/2] run-command: mark path lookup errors with ENOENT Jeff King
2018-10-24 9:01 ` Johannes Schindelin
2018-10-24 9:16 ` Jeff King
2018-10-24 9: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=20181024073637.GA31069@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).