From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org, Ben Walton <bwalton@artsci.utoronto.ca>
Subject: Re: [PATCH] documentation: Makefile accounts for SHELL_PATH setting
Date: Sat, 11 Apr 2009 13:42:39 -0700 [thread overview]
Message-ID: <7vmyamdirk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090410093430.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Fri, 10 Apr 2009 09:34:30 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> Quoting Ben Walton:
>
>> Ensure that the Makefile that generates and installs the Documentation
>> is aware of any SHELL_PATH setting. Use this value if found or the
>> current setting for SHELL if not. This is an accommodation for systems
>> where sh is not bash.
>>
>> Signed-off-by: Ben Walton <bwalton@artsci.utoronto.ca>
>
> Junio, may I ask what happened to this patch?
There was a discussion going that eventurally petered out without seeing
success (or breakage) reports from people with various platforms.
I think the patch text is Ok, with "where sh is not bash" in the log
message rephrased to "where sh is not POSIX", but I do not have an easy
access to a system where /bin/sh is broken (perhaps I should install
OpenSolaris in a vbox to try out), so it is still sitting in my inbox.
next prev parent reply other threads:[~2009-04-11 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 13:20 [PATCH] documentation: Makefile accounts for SHELL_PATH setting Ben Walton
2009-03-23 6:57 ` Jeff King
2009-03-23 12:57 ` Ben Walton
2009-03-23 14:03 ` Jeff King
2009-03-23 14:12 ` Mike Hommey
2009-04-10 0:34 ` Nanako Shiraishi
2009-04-11 20:42 ` Junio C Hamano [this message]
2009-04-12 1:49 ` Ben Walton
2009-04-12 8:28 ` Junio C Hamano
2009-04-13 14:21 ` Ben Walton
-- strict thread matches above, loose matches on Subject: below --
2009-03-21 2:40 Ben Walton
2009-03-21 3:22 ` Jeff King
2009-03-21 11:38 ` Ben Walton
2009-03-22 6:19 ` Jeff King
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=7vmyamdirk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.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).