From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Poornima Nayak <poornima.nayak@in.ibm.com>,
ltp-list@lists.sourceforge.net,
Mike Frysinger <vapier@gentoo.org>,
Daniel Lezcano <daniel.lezcano@free.fr>,
Veerendra C <vechandr@in.ibm.com>,
Munipradeep <mbeeraka@in.ibm.com>
Subject: Re: [LTP] [PATCH 4/4] netns: Change interpretters from sh to bash
Date: Mon, 06 Jul 2009 21:20:45 +0530 [thread overview]
Message-ID: <1246895446.4887.50.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20090702203253.GI19135@count0.beaverton.ibm.com>
On Thu, 2009-07-02 at 13:32 -0700, Matt Helsley wrote:
> On Thu, Jul 02, 2009 at 02:35:46PM -0400, Mike Frysinger wrote:
> > On Thursday 02 July 2009 05:05:32 Matt Helsley wrote:
> > > As best I can tell these tests do not use true sh syntax -- they use bash
> > > syntax. Rather than bother hunting down all the bash-isms just convert
> > > them to use bash as their interpretter.
> >
> > the changelog doesnt seem to jive with the commit. if you were merely
> > changing the shebang, why did you also fix the bashisms like s/==/-eq/ ?
>
> Good point -- it does make the == -> -eq and the || -> -o conversions
> pointless.
>
> >
> > at any rate, someone (i dont recall who) posted fixes to these files recently
> > to de-bashify them. there was some feedback though, so perhaps you should
> > address those minor issues and submit an updated patch.
>
> OK, I'll look for that patch and consider it as a replacement for 3 and 4 of
> this series.
Will wait for this from you.
Regards--
Subrata
>
> >
> > in general, converting sh to bash is a bad idea as it can cause issues for us
> > embedded peeps.
> > -mike
>
> I suppose that's because of the memory bash consumes. Is there anything else
> it does which is bad for embedded?
>
> Cheers,
> -Matt Helsley
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-06 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 8:48 [LTP] [PATCH 1/4] netns: Report version of iproute2 tools in ver_linux Matt Helsley
2009-07-02 8:58 ` [LTP] [PATCH 2/4] netns: Add ip tools check to netns tests Matt Helsley
2009-07-06 15:50 ` Subrata Modak
2009-07-02 9:02 ` [LTP] [PATCH 3/4] netns: Fixup non-sh syntax Matt Helsley
2009-07-03 3:33 ` Garrett Cooper
2009-07-02 9:05 ` [LTP] [PATCH 4/4] netns: Change interpretters from sh to bash Matt Helsley
2009-07-02 18:35 ` Mike Frysinger
2009-07-02 20:32 ` Matt Helsley
2009-07-02 22:09 ` Mike Frysinger
2009-07-06 21:51 ` [LTP] [PATCH] Remove bashisms (WAS Re: [PATCH 4/4] netns: Change interpretters from sh to bash) Matt Helsley
2009-07-06 21:57 ` Garrett Cooper
2009-07-06 23:10 ` Jiří Paleček
2009-07-06 23:24 ` Mike Frysinger
2009-07-07 1:30 ` Matt Helsley
2009-07-06 15:50 ` Subrata Modak [this message]
2009-07-06 15:50 ` [LTP] [PATCH 1/4] netns: Report version of iproute2 tools in ver_linux Subrata Modak
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=1246895446.4887.50.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=daniel.lezcano@free.fr \
--cc=ltp-list@lists.sourceforge.net \
--cc=matthltc@us.ibm.com \
--cc=mbeeraka@in.ibm.com \
--cc=poornima.nayak@in.ibm.com \
--cc=vapier@gentoo.org \
--cc=vechandr@in.ibm.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