From: Andreas Schwab <schwab@linux-m68k.org>
To: "Cristian Rodríguez via Libc-alpha" <libc-alpha@sourceware.org>
Cc: "Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>,
"Joe Simmons-Talbott" <josimmon@redhat.com>
Subject: Re: [PATCH] system: Add "--" after "-c" for sh (BZ #28519)
Date: Mon, 27 Mar 2023 22:12:10 +0200 [thread overview]
Message-ID: <875yam3qed.fsf@igel.home> (raw)
In-Reply-To: <CAPBLoAe_VCPNr-Z9v8BQcxV2dRanfv2Gm6YU-NvANQ8VLrzAaQ@mail.gmail.com> ("Cristian =?utf-8?Q?Rodr=C3=ADguez?= via Libc-alpha"'s message of "Mon, 27 Mar 2023 16:34:28 -0300")
On Mär 27 2023, Cristian Rodríguez via Libc-alpha wrote:
> On Mon, Mar 27, 2023 at 3:56 PM Adhemerval Zanella Netto via
> Libc-alpha <libc-alpha@sourceware.org> wrote:
>
>> I am not sure if it should be ok to break such environments, at least there are
>> available shells in some environments.
>
> Isn't a posix compliant shell already required as "/bin/sh" ?
It must be Bourne-compatible anyway, so (t)csh is out.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2023-03-27 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 18:04 Joe Simmons-Talbott
2023-03-27 18:56 ` Adhemerval Zanella Netto
2023-03-27 19:34 ` Cristian Rodríguez
2023-03-27 19:50 ` Zack Weinberg
2023-03-27 19:56 ` Adhemerval Zanella Netto
2023-03-27 20:14 ` Cristian Rodríguez
2023-03-28 12:52 ` Joe Simmons-Talbott
2023-03-28 13:02 ` Adhemerval Zanella Netto
2023-03-27 20:12 ` Andreas Schwab [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=875yam3qed.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=adhemerval.zanella@linaro.org \
--cc=crrodriguez@opensuse.org \
--cc=josimmon@redhat.com \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).