public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Policy regarding BASH
Date: Mon, 14 Oct 2013 01:33:14 -0400	[thread overview]
Message-ID: <201310140133.16162.vapier@gentoo.org> (raw)
In-Reply-To: <20130919134049.GA14290@rei>


[-- Attachment #1.1: Type: Text/Plain, Size: 432 bytes --]

On Thursday 19 September 2013 09:40:50 chrubis@suse.cz wrote:
> > So what is the policy regarding bash presence in LTP? Is it permitted to
> > write testcases using bash specific features?
> > Or are we strongly encouraged to use "common shell" only?
> 
> Just fix the tests to work with common shell and send a patch.

and please do not do it blindly.  running `checkbashisms` is known to produce 
false positives.
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 416 bytes --]

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2013-10-14  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 12:47 [LTP] Policy regarding BASH Stanislav Kholmanskikh
2013-09-19 12:50 ` Stanislav Kholmanskikh
2013-09-19 13:40 ` chrubis
2013-10-14  5:33   ` Mike Frysinger [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=201310140133.16162.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=ltp-list@lists.sourceforge.net \
    /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