Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 01/20] smstools: fix PN -> BPN for multilib
Date: Tue, 12 May 2015 18:19:06 -0400	[thread overview]
Message-ID: <55527C5A.4010900@gmail.com> (raw)
In-Reply-To: <20150512144510.GC2714@jama>

On 05/12/15 10:45, Martin Jansa wrote:
> On Tue, May 12, 2015 at 01:43:19PM +0100, Paul Eggleton wrote:
>> On Monday 11 May 2015 11:27:04 Martin Jansa wrote:
>>> On Fri, May 08, 2015 at 03:42:16PM +0800, Yi Zhao wrote:
>>>> Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
>>> Changes 03, 18, 20 didn't make it to patchwork, because they were marked
>>> as Spam by gmail
>> Hang on, I'm confused. Why should the patches being marked as spam in gmail 
>> have any bearing on whether they should show up in patchwork? Surely gmail 
>> shouldn't be involved in the sending part, only subsequently when the mail is 
>> sent from the mailing list to you (since you use gmail)?
> Isn't patchwork reading some gmail account over imap?
>
> The list of patches not appearing in patchwork is exactly matching with
> patches marked as spam in my inbox, so I believe that the same is
> happening in patchwork's gmail account.

Does anyone know if it helps when I notice them in "Spam" and mark them
as "Not Spam"?


  parent reply	other threads:[~2015-05-12 22:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  7:42 [meta-oe][PATCH 01/20] smstools: fix PN -> BPN for multilib Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 02/20] hexedit: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 03/20] p7zip: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 04/20] fbgrab: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 05/20] takao-fonts: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 06/20] xbitmaps: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 07/20] gpsd: " Yi Zhao
2015-05-11 11:48   ` Philip Balister
2015-05-11 11:52     ` Martin Jansa
2015-05-08  7:42 ` [meta-oe][PATCH 08/20] navit: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 09/20] omgps: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 10/20] orrery: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 11/20] fltk: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 12/20] mime-support: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 13/20] openct: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 14/20] picocom: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 15/20] soci: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 16/20] mozjs: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 17/20] iperf: fix ${PN}-${PV} -> ${BP} " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 18/20] mpich: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 19/20] synergy: " Yi Zhao
2015-05-08  7:42 ` [meta-oe][PATCH 20/20] sylpheed: remove do_install_append Yi Zhao
2015-05-11  9:27 ` [meta-oe][PATCH 01/20] smstools: fix PN -> BPN for multilib Martin Jansa
2015-05-12  7:14   ` Yi Zhao
2015-05-12 12:43   ` Paul Eggleton
2015-05-12 14:45     ` Martin Jansa
2015-05-12 14:50       ` Paul Eggleton
2015-05-12 16:09         ` Khem Raj
2015-05-12 16:15           ` Paul Eggleton
2015-05-12 16:50             ` Khem Raj
2015-05-12 22:19       ` Trevor Woerner [this message]
2015-05-12 22:28         ` Martin Jansa

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=55527C5A.4010900@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-devel@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