From: Philip Balister <philip@balister.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH] python-vcversioner: Fix bad DESCRIPTION and HOMEPAGE entries.
Date: Tue, 2 Feb 2016 09:07:33 +0100 [thread overview]
Message-ID: <56B063C5.8070202@balister.org> (raw)
In-Reply-To: <5510016.r0vissdbSN@peggleto-mobl.ger.corp.intel.com>
On 01/28/2016 06:34 PM, Paul Eggleton wrote:
> On Thu, 28 Jan 2016 11:22:57 Philip Balister wrote:
>> Copy/paste is the root of all evil.
>>
>> Signed-off-by: Philip Balister <philip@balister.org>
>> ---
>> meta-python/recipes-devtools/python/python-vcversioner_2.14.0.0.bb | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git
>> a/meta-python/recipes-devtools/python/python-vcversioner_2.14.0.0.bb
>> b/meta-python/recipes-devtools/python/python-vcversioner_2.14.0.0.bb index
>> 152034b..6c96875 100644
>> --- a/meta-python/recipes-devtools/python/python-vcversioner_2.14.0.0.bb
>> +++ b/meta-python/recipes-devtools/python/python-vcversioner_2.14.0.0.bb
>> @@ -1,5 +1,5 @@
>> -DESCRIPTION = "Twisted Web Sockets"
>> -HOMEPAGE = "https://github.com/MostAwesomeDude/txWS"
>> +DESCRIPTION = "Python vcversioner"
>> +HOMEPAGE = "https://github.com/habnabit/vcversioner"
>
> Sorry to pick on this, I know you're fixing a completely wrong description,
> but:
>
> * Short descriptions should go in SUMMARY
> * This is a pretty useless short description, it doesn't do anything beyond
> what the recipe name does.
Can you remind us what fields the layer index is using? I noticed the
issue using the layer index to look somehting up.
Philip
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2016-02-02 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 16:22 [meta-python][PATCH] python-vcversioner: Fix bad DESCRIPTION and HOMEPAGE entries Philip Balister
2016-01-28 17:34 ` Paul Eggleton
2016-02-02 8:07 ` Philip Balister [this message]
2016-02-02 8:30 ` Paul Eggleton
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=56B063C5.8070202@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.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