Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Jose Lamego <jose.a.lamego@linux.intel.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] manpages.bbclass: avoid QA warning when "manpages" feature not supported
Date: Thu, 25 May 2017 11:06:11 +0300	[thread overview]
Message-ID: <128b693d-588c-e1be-0720-6c6954b4651c@linux.intel.com> (raw)
In-Reply-To: <3a84eeba-58d0-bf74-61c3-b3b0d5292ad6@linux.intel.com>

On 05/24/2017 11:54 PM, Jose Lamego wrote:
> Sorry is miss this message.
>
> The command line is missing the squared brackets (the following should
> do the work since I may have permissions):
>
> [Patchwork-Status: Rejected]
>
> Guys: Do you believe we should drop the brackets requirement?

You can support both brackets and no-brackets.

The problem is that this feature is not documented, nobody knows about 
it, and we lack established practices around it. Who should be using it? 
I'd say only the author of the patch or people with commit rights to 
master (RP, Ross).

Alex



  parent reply	other threads:[~2017-05-25  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  8:32 [PATCH] manpages.bbclass: avoid QA warning when "manpages" feature not supported Patrick Ohly
2017-05-15 11:47 ` Alexander Kanavin
2017-05-15 12:24   ` Patrick Ohly
2017-05-15 13:06     ` Burton, Ross
2017-05-24 20:54       ` Jose Lamego
2017-05-24 20:57         ` Jose Lamego
2017-05-25  8:06         ` Alexander Kanavin [this message]
2017-05-25 14:21           ` Jose Lamego

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=128b693d-588c-e1be-0720-6c6954b4651c@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=jose.a.lamego@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