From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
Martin Jansa <martin.jansa@gmail.com>
Subject: Re: ✗ patchtest: failure for license.bbclass: be a bit more strict when searching ${PN}-${LICENSE_PACKAGE_SUFFIX} in packages
Date: Mon, 9 Apr 2018 09:08:37 +0300 [thread overview]
Message-ID: <2b8b89f3-434b-949a-ad68-d1b9a9ab1efa@linux.intel.com> (raw)
In-Reply-To: <20180408203419.2390.23424@do.openembedded.org>
On 04/08/2018 11:34 PM, Patchwork wrote:
>
> * Patch license.bbclass: be a bit more strict when searching ${PN}-${LICENSE_PACKAGE_SUFFIX} in packages
> Issue Commit shortlog is too long [test_shortlog_length]
> Suggested fix Edit shortlog so that it is 90 characters or less (currently 96 characters)
We should probably remove this limit. Commit shortlog should contain a
description of the change in a single sentence; it is not always
possible to cram that into 90 characters (or any arbitrarily chosen
amount of characters, really).
Alex
prev parent reply other threads:[~2018-04-09 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 20:16 [PATCH] license.bbclass: be a bit more strict when searching ${PN}-${LICENSE_PACKAGE_SUFFIX} in packages Martin Jansa
2018-04-08 20:34 ` ✗ patchtest: failure for " Patchwork
2018-04-09 6:08 ` Alexander Kanavin [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=2b8b89f3-434b-949a-ad68-d1b9a9ab1efa@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.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