From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Clean-up of /bin/sh patching
Date: Thu, 05 Jan 2017 18:10:47 +0100 [thread overview]
Message-ID: <8760ltjuug.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <cover.1483633538.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-05 17:10 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 ` Marius Bakke [this message]
2017-01-05 23:12 ` [PATCH 0/5] Clean-up of /bin/sh patching Ludovic Courtès
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=8760ltjuug.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.