From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Arkadiusz Miskiewicz <arekm@maven.pl>,
Oleg Verych <olecom@flower.upol.cz>,
Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
Date: Sat, 23 Jun 2007 16:34:42 +0200 [thread overview]
Message-ID: <200706231634.42907.ak@suse.de> (raw)
In-Reply-To: <20070623153239.78ee86fe@the-village.bc.nu>
On Saturday 23 June 2007 16:32:39 Alan Cox wrote:
> Having the scripts work with other shells is very helpful for porting,
> cross building and the like.
Well then for the majority of cross compile users you should consequently write
them in Windows batch language.
> Also on Linux /bin/sh is not
> neccessarily /bin/bash.
If it's not I think these few distributions give Linux a bad name
because they introduce quite unnecessary incompatibilities.
Hopefully they are not widely used.
-Andi
next prev parent reply other threads:[~2007-06-23 14:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 5:51 [PATCH] doc/oops-tracing: add Code: decode info Randy Dunlap
2007-06-22 14:26 ` Andi Kleen
2007-06-22 16:44 ` [PATCH v2] " Randy Dunlap
2007-06-22 17:23 ` Andi Kleen
2007-06-22 18:25 ` Randy Dunlap
2007-06-22 21:29 ` Andi Kleen
2007-06-22 20:28 ` [PATCH v3] " Randy Dunlap
2007-06-23 8:34 ` NAK (bashizm in the /bin/sh script): " Oleg Verych
2007-06-23 11:00 ` Andi Kleen
2007-06-23 11:09 ` Arkadiusz Miskiewicz
2007-06-23 13:17 ` Andi Kleen
2007-06-23 13:26 ` Willy Tarreau
2007-06-23 13:51 ` [OT]Re: " Oleg Verych
2007-06-23 13:47 ` Björn Steinbrink
2007-06-23 14:24 ` Arkadiusz Miskiewicz
2007-06-23 14:32 ` Alan Cox
2007-06-23 14:34 ` Andi Kleen [this message]
2007-06-23 14:48 ` Alan Cox
2007-06-23 15:35 ` Segher Boessenkool
2007-06-23 14:38 ` Sean
2007-06-23 15:23 ` Oleg Verych
2007-06-23 17:43 ` Randy Dunlap
2007-06-23 17:56 ` Andrew Morton
2007-06-23 20:54 ` Adrian Bunk
2007-06-23 21:04 ` Randy Dunlap
2007-06-23 20:24 ` Matthieu CASTET
2007-06-26 10:16 ` DervishD
2007-06-26 10:24 ` Jan-Benedict Glaw
2007-06-26 15:33 ` DervishD
2007-06-26 16:04 ` Randy Dunlap
2007-06-26 17:03 ` DervishD
2007-06-26 10:50 ` Arne Georg Gleditsch
2007-06-26 15:36 ` DervishD
2007-06-26 17:19 ` Randy Dunlap
2007-06-26 17:25 ` Julio M. Merino Vidal
2007-06-26 17:56 ` Randy Dunlap
2007-06-28 7:58 ` Arne Georg Gleditsch
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=200706231634.42907.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arekm@maven.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=randy.dunlap@oracle.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 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.