From: "Burton, Ross" <ross.burton@intel.com>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libxml2: 2.9.4 -> 2.9.5
Date: Thu, 28 Sep 2017 11:24:02 +0100 [thread overview]
Message-ID: <CAJTo0LaNBhZMR5ufy8=f2h4mHD2u_j8uLxWhs_TdWTMNNPM=xQ@mail.gmail.com> (raw)
In-Reply-To: <617e9e3d-e7a4-ea73-9f9c-10ca4c46c441@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
On 28 September 2017 at 11:14, Andrej Valek <andrej.valek@siemens.com>
wrote:
> Of course, but there is a problem with mailing list encoding. This is
> the reason, why is pushed into branch.
>
I understand, and I will be pulling from the branch, but review is on the
list so patches need to be on the list.
Ross
[-- Attachment #2: Type: text/html, Size: 660 bytes --]
next prev parent reply other threads:[~2017-09-28 10:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 6:35 [PATCH] libxml2: 2.9.4 -> 2.9.5 Andrej Valek
2017-09-05 9:19 ` Burton, Ross
2017-09-05 17:28 ` Andrej Valek
2017-09-05 18:52 ` Burton, Ross
2017-09-06 6:16 ` Andrej Valek
2017-09-27 8:52 ` Andrej Valek
2017-09-27 15:35 ` Burton, Ross
2017-09-28 6:06 ` Andrej Valek
2017-09-28 9:34 ` Burton, Ross
2017-09-28 10:14 ` Andrej Valek
2017-09-28 10:24 ` Burton, Ross [this message]
2017-09-28 12:06 ` [PATCH v2] " Andrej Valek
2017-09-28 16:18 ` Burton, Ross
2017-09-29 7:16 ` Andrej Valek
2017-09-29 7:08 ` [PATCH v3] " Andrej Valek
2017-10-06 7:27 ` [PATCH v3] libxml2: 2.9.4 -> 2.9.6 Andrej Valek
2017-10-06 12:11 ` Alexander Kanavin
2017-10-06 13:19 ` Andrej Valek
2017-10-06 13:59 ` Alexander Kanavin
2017-11-06 7:34 ` Andrej Valek
2017-10-09 6:29 ` [PATCH v4] " Andrej Valek
2017-10-31 7:03 ` [PATCH v5] " Andrej Valek
2017-11-03 7:12 ` [PATCH v6] libxml2: 2.9.4 -> 2.9.7 Andrej Valek
2017-11-06 7:37 ` Andrej Valek
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='CAJTo0LaNBhZMR5ufy8=f2h4mHD2u_j8uLxWhs_TdWTMNNPM=xQ@mail.gmail.com' \
--to=ross.burton@intel.com \
--cc=andrej.valek@siemens.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 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.