From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/2] insane.bbclass: Check for invalid characters (non UTF8) on recipe metadata
Date: Wed, 26 Aug 2015 11:13:50 -0500 [thread overview]
Message-ID: <55DDE5BE.9020405@linux.intel.com> (raw)
In-Reply-To: <CABcZANkAWDD5Heo+gd4G+dVuOakL1tf7qt6Qz0-Teq6_FVCDaQ@mail.gmail.com>
hi Chris,
On 08/17/2015 05:57 PM, Christopher Larson wrote:
> On Mon, Aug 17, 2015 at 12:10 AM, <
> leonardo.sandoval.gonzalez@linux.intel.com> wrote:
>
>> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
>>
>> Check if invalid characters are present on recipe's metadata. Fields
>> taken into account are: 'DESCRIPTION', 'SUMMARY', 'LICENSE' and 'SECTION'.
>>
>> Signed-off-by: Leonardo Sandoval <
>> leonardo.sandoval.gonzalez@linux.intel.com>
>>
>
> This commit message doesn't define what "invalid" is.
Looking it closely, the commit message does include in parenthesis what
is meant by 'invalid'.
Any concert about this definition?
>
next prev parent reply other threads:[~2015-08-26 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 7:10 [PATCH v2 0/2] Check invalid characters on some recipe metadata leonardo.sandoval.gonzalez
2015-08-17 7:10 ` [PATCH v2 1/2] insane.bbclass: Check for invalid characters (non UTF8) on " leonardo.sandoval.gonzalez
2015-08-17 22:57 ` Christopher Larson
2015-08-25 14:27 ` Leonardo Sandoval
2015-08-26 16:13 ` Leonardo Sandoval [this message]
2015-08-26 16:15 ` Christopher Larson
2015-08-17 7:10 ` [PATCH v2 2/2] package_deb.bbclass: Allow UTF-8 characters on control files leonardo.sandoval.gonzalez
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=55DDE5BE.9020405@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=clarson@kergoth.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