Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "dengke.du@windriver.com" <dengke.du@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org >> Patches and
	discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: bash: remove the format string "%q" in the unicode3.sub
Date: Thu, 11 Aug 2016 16:53:34 +0800	[thread overview]
Message-ID: <57AC3D0E.9010502@windriver.com> (raw)
In-Reply-To: <bfe3a375-f09b-7617-c209-0df28b24325a@case.edu>

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

Hi ross

After querying for the current maintainer of bash Chet Ramey, he said 
the devel
branch of bash have fixed it. So I will import those patchs later for 
the bash tests
suite.

We can check the patchs at:

http://git.savannah.gnu.org/cgit/bash.git/commit/tests/intl.right?h=devel&id=85ec0778f9d778e1820fb8c0e3e996f2d1103b45
http://git.savannah.gnu.org/cgit/bash.git/diff/tests/intl.right?h=devel&id=74b8cbb41398b4453d8ba04d0cdd1b25f9dcb9e3

//dengke


-------- Forwarded Message --------
Subject: 	Re: bash: remove the format string "%q" in the unicode3.sub
Date: 	Tue, 9 Aug 2016 10:39:13 -0400
From: 	Chet Ramey <chet.ramey@case.edu>
Reply-To: 	chet.ramey@case.edu
To: 	dengke.du@windriver.com <dengke.du@windriver.com>, bug-bash@gnu.org
CC: 	chet.ramey@case.edu



On 8/9/16 3:18 AM, dengke.du@windriver.com wrote:
> Hi all
>
> When I run the tests for the bash, the sub-test unicode3.sub of intl.tests
> failed.
>
> The sub-test unicode3.sub contain the following:
>
>     payload=$'\065\247\100\063\231\053\306\123\070\237\242\352\263'
>     "$payload"
>     printf %q "$payload"
>
> In this situation, the format string "%q" in command printf means that when the
> character in the payload is not in {alpha & digit & punctuation & ISO
> 646(7-bit)}, it
> would print the string with ANSI-C style quoted string: $'...' , we can
> check the source code

This has already been changed in the devel branch (back in May, 2015), and
the test case and tets output was changed at the same time.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/




[-- Attachment #2: Type: text/html, Size: 4189 bytes --]

       reply	other threads:[~2016-08-11  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bfe3a375-f09b-7617-c209-0df28b24325a@case.edu>
2016-08-11  8:53 ` dengke.du [this message]
2016-08-11  9:22   ` bash: remove the format string "%q" in the unicode3.sub Burton, Ross

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=57AC3D0E.9010502@windriver.com \
    --to=dengke.du@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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