From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] package_ipk: correct ipk descriptions
Date: Wed, 24 May 2017 15:47:44 -0500 [thread overview]
Message-ID: <1495658864.26945.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaJrNTwML2jQbPR+p5y3EOnwm=D2nDiD5VcHtfer8m+gA@mail.gmail.com>
On Wed, 2017-05-24 at 21:15 +0100, Burton, Ross wrote:
>
> On 22 May 2017 at 17:43, <leonardo.sandoval.gonzalez@linux.intel.com>
> wrote:
> Empty descriptions are set with a space following by a dot.
> For the non-empty ones,
> there is no need for formating the description with textwrap,
> so remove the logic
> for the latter.
>
>
> Looks like opkg doesn't behave like this as building lzop fails (which
> has lots of newlines embedded in the SUMMARY).
I will check that particular recipe and bb world just so see if some
other recipe is broken with this change, then provide a v3.
Leo
>
>
> Ross
next prev parent reply other threads:[~2017-05-24 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 19:26 [PATCH] package_ipk.bbclass: Include a space followed by a dot for empty description lines leonardo.sandoval.gonzalez
2017-05-04 11:13 ` Burton, Ross
2017-05-22 16:43 ` [PATCH v2] package_ipk: correct ipk descriptions leonardo.sandoval.gonzalez
2017-05-24 20:15 ` Burton, Ross
2017-05-24 20:47 ` Leonardo Sandoval [this message]
2017-05-24 22:08 ` Burton, Ross
2017-05-29 17:24 ` Leonardo Sandoval
2017-05-29 17:36 ` [PATCH v3] package_ipk: correct ipk multiline descriptions leonardo.sandoval.gonzalez
2017-05-29 21:41 ` Andreas Oberritter
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=1495658864.26945.1.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.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