From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <saul.wold@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues
Date: Tue, 22 Mar 2016 08:57:19 +0000 [thread overview]
Message-ID: <1458637039.20442.34.camel@linuxfoundation.org> (raw)
In-Reply-To: <1458611456.5327.25.camel@intel.com>
On Mon, 2016-03-21 at 18:50 -0700, Saul Wold wrote:
> Did this v2 get missed? I see the first patch got merged.
Clearly it got missed sorry.
I appreciate that is frustrating for people, equally, we do some level
of testing of changes going in, which introduces delay and when you
have ~80 patches you're about to merge and scan the lists for new
versions, its sometimes hard to catch everything :(.
Its also even harder when the v2 is buried in some random git branch
somewhere which I appreciate in this case it wasn't but does cause
problems in general.
Cheers,
Richard
prev parent reply other threads:[~2016-03-22 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 21:24 [PATCH v2] parselogs: add new whitelist entries to address 4.4.3 issues Saul Wold
2016-03-22 1:50 ` Saul Wold
2016-03-22 8:57 ` Richard Purdie [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=1458637039.20442.34.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.