From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Where are my patches?
Date: Wed, 10 Mar 2010 18:35:20 +0000 [thread overview]
Message-ID: <1268246120.14566.1078.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <d1ded4381003100919y125959b5m3198c8d848661187@mail.gmail.com>
On Wed, 2010-03-10 at 11:19 -0600, Adrian Alonso wrote:
> But still patch's don't reach oe-patchwork.
>
> Any advise?
If your patches are reaching the list then it is probably nothing within
your control. I think some folks have had trouble with patchwork's spam
filtering in the past.
In any case, it isn't necessary for your patch to appear in patchwork in
order for it to be actioned, so there is no need to worry about it too
much.
p.
next prev parent reply other threads:[~2010-03-10 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 10:58 Where are my patches? Sledz, Steffen
2010-03-10 16:02 ` Steffen Sledz
2010-03-10 17:19 ` Adrian Alonso
2010-03-10 18:35 ` Phil Blundell [this message]
2010-03-10 19:16 ` Tom Rini
2010-03-11 7:00 ` Steffen Sledz
2010-03-11 7:59 ` Frans Meulenbroeks
2010-03-11 8:13 ` Steffen Sledz
2010-03-11 15:56 ` Tom Rini
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=1268246120.14566.1078.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--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