From: Javier Viguera <javier.viguera@digi.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files: fix 'dash' expanding '\n'
Date: Tue, 26 Feb 2013 18:24:14 +0100 [thread overview]
Message-ID: <512CEFBE.4010901@digi.com> (raw)
In-Reply-To: <1361372957-38860-1-git-send-email-javier.viguera@digi.com>
Hi all,
I just saw this patch i sent last week was pushed to
openembedded-core/poky *master* branches. Thanks for that.
But in my development i am using stable 'danny' branches.
Any chance that this patch gets cherry-picked to 'danny' on
openembedded-core and poky repos?
-
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.
On 02/20/2013 04:09 PM, Javier Viguera wrote:
> Dash's 'echo' command expands '\n' by default, so the '\n' is not
> included in the '/etc/issue' file.
>
> Use 'printf' for portability between different shells.
>
> Signed-off-by: Javier Viguera <javier.viguera@digi.com>
> ---
>
> Probably also worth to be cherry-picked to 'danny' branch.
>
> meta/recipes-core/base-files/base-files_3.0.14.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb b/meta/recipes-core/base-files/base-files_3.0.14.bb
> index 6a3db50..e7a9d82 100644
> --- a/meta/recipes-core/base-files/base-files_3.0.14.bb
> +++ b/meta/recipes-core/base-files/base-files_3.0.14.bb
> @@ -129,7 +129,7 @@ do_install_basefilesissue () {
> printf "${DISTRO_VERSION} " >> ${D}${sysconfdir}/issue
> printf "${DISTRO_VERSION} " >> ${D}${sysconfdir}/issue.net
> fi
> - echo "\n \l" >> ${D}${sysconfdir}/issue
> + printf "\\\n \\\l\n" >> ${D}${sysconfdir}/issue
> echo >> ${D}${sysconfdir}/issue
> echo "%h" >> ${D}${sysconfdir}/issue.net
> echo >> ${D}${sysconfdir}/issue.net
>
next prev parent reply other threads:[~2013-02-26 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 15:09 [PATCH] base-files: fix 'dash' expanding '\n' Javier Viguera
2013-02-26 17:24 ` Javier Viguera [this message]
2013-02-26 17:29 ` Saul Wold
2013-02-27 13:48 ` 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=512CEFBE.4010901@digi.com \
--to=javier.viguera@digi.com \
--cc=openembedded-core@lists.openembedded.org \
/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