From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Clean-up of /bin/sh patching
Date: Fri, 06 Jan 2017 00:12:41 +0100 [thread overview]
Message-ID: <87vatt2j9y.fsf@gnu.org> (raw)
In-Reply-To: <8760ltjuug.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Thu, 05 Jan 2017 18:10:47 +0100")
Marius Bakke <mbakke@fastmail.com> skribis:
> Leo Famulari <leo@famulari.name> writes:
>
>> This patch series changes all the instances of /bin/sh being patched to
>> /bin/bash that I can find.
>>
>> They are for core-updates.
>
> [...]
>
>> Leo Famulari (5):
>> gnu: m4: Don't replace 'sh' reference with 'bash'.
>> gnu: gnu-make: Don't replace 'sh' reference with 'bash'.
>> gnu: glibc/linux: Don't replace 'sh' reference with 'bash'.
>> gnu: glibc/linux: Use /bin/sh instead of /bin/bash as the default
>> shell.
>> gnu: gawk: Don't replace 'sh' reference with 'bash'.
>
> Thanks! I've verified all of these and they LGTM. Good catch on the make
> and glibc paths.h substitutions.
+1!
Ludo’.
prev parent reply other threads:[~2017-01-05 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:28 [PATCH 0/5] Clean-up of /bin/sh patching Leo Famulari
2017-01-05 16:28 ` [PATCH 1/5] gnu: m4: Don't replace 'sh' reference with 'bash' Leo Famulari
2017-01-05 16:28 ` [PATCH 2/5] gnu: gnu-make: " Leo Famulari
2017-01-05 17:14 ` Marius Bakke
2017-01-05 17:40 ` Leo Famulari
2017-01-05 16:28 ` [PATCH 3/5] gnu: glibc/linux: " Leo Famulari
2017-01-05 16:28 ` [PATCH 4/5] gnu: glibc/linux: Use /bin/sh instead of /bin/bash as the default shell Leo Famulari
2017-01-05 16:28 ` [PATCH 5/5] gnu: gawk: Don't replace 'sh' reference with 'bash' Leo Famulari
2017-01-05 17:10 ` [PATCH 0/5] Clean-up of /bin/sh patching Marius Bakke
2017-01-05 23:12 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vatt2j9y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).