From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Plauchu Edwin <edwin.plauchu.camacho@linux.intel.com>,
openembedded-core@lists.openembedded.org
Cc: joshua.g.lock@intel.com, Edwin Plauchu <edwin.plauchu.camacho@intel.com>
Subject: Re: [PATCH v1] unzip: fix security issues
Date: Mon, 30 May 2016 22:42:39 +0100 [thread overview]
Message-ID: <1464644559.19134.106.camel@linuxfoundation.org> (raw)
In-Reply-To: <574C5E1E.3020800@linux.intel.com>
On Mon, 2016-05-30 at 10:37 -0500, Plauchu Edwin wrote:
> Ping!
You sent this patch late on Friday. Sending a ping by midday on Monday
isn't going to help. If you read the project status email, you'd notice
that I've been away for a couple of days. Its also a holiday in the UK
and US today. We're also struggling with patch review anyway and there
are other patches ahead of yours in the queue.
Please be a bit more patient.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-30 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 20:29 [PATCH v1] unzip: fix security issues Edwin Plauchu
2016-05-30 15:37 ` Plauchu Edwin
2016-05-30 21:42 ` Richard Purdie [this message]
2016-06-07 21:49 ` Plauchu Edwin
2016-06-08 13:30 ` Burton, Ross
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=1464644559.19134.106.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=edwin.plauchu.camacho@intel.com \
--cc=edwin.plauchu.camacho@linux.intel.com \
--cc=joshua.g.lock@intel.com \
--cc=openembedded-core@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