public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arne Georg Gleditsch <argggh@dolphinics.no>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Julio M. Merino Vidal" <jmerino@ac.upc.edu>,
	Oleg Verych <olecom@flower.upol.cz>, Andi Kleen <ak@suse.de>,
	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: Thu, 28 Jun 2007 09:58:45 +0200	[thread overview]
Message-ID: <871wfwik7e.fsf@pelargir.dolphinics.no> (raw)
In-Reply-To: <20070626105602.8bae494b.randy.dunlap@oracle.com> (Randy Dunlap's message of "Tue\, 26 Jun 2007 10\:56\:02 -0700")

Randy Dunlap <randy.dunlap@oracle.com> writes:
> On Tue, 26 Jun 2007 19:25:00 +0200 Julio M. Merino Vidal wrote:
>> The correct expression could be $((${a} + 2)).  Tested under NetBSD's  
>> sh, which is very POSIX-compliant.
>
> Thanks.  Does anyone see other changes that are needed?

[..]

> and the complete script is:

Both busybox sh and dash are happy with this.  (Or rather, busybox
would be if its mktemp hadn't been broken.)

-- 
								Arne.

      reply	other threads:[~2007-06-28  7:58 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
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 [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=871wfwik7e.fsf@pelargir.dolphinics.no \
    --to=argggh@dolphinics.no \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jmerino@ac.upc.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox