From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [Master][PATCH] libtiff: Update to 4.0.7
Date: Thu, 1 Dec 2016 16:08:56 +0200 [thread overview]
Message-ID: <a3b8dd3c-02c6-8580-32b4-61db8848dab8@linux.intel.com> (raw)
In-Reply-To: <61bcea65-f891-2914-27a4-e788fc517cde@gmail.com>
On 11/23/2016 05:32 PM, akuster808 wrote:
> The never made into patchwork. is there a bug there ? is there an issue
> on how I submitted?
>
> - armin
>
>
> On 11/21/2016 09:28 PM, Armin Kuster wrote:
I haven't actually seen the email with the patch at all on the mailing
list, just your response to it. Can you resend?
Alex
prev parent reply other threads:[~2016-12-01 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1479792499-19369-1-git-send-email-akuster@mvista.com>
2016-11-23 15:32 ` [Master][PATCH] libtiff: Update to 4.0.7 akuster808
2016-11-23 16:04 ` Burton, Ross
2016-11-26 15:35 ` akuster808
2016-12-01 14:08 ` Alexander Kanavin [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=a3b8dd3c-02c6-8580-32b4-61db8848dab8@linux.intel.com \
--to=alexander.kanavin@linux.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