From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andrej Valek <andrej.valek@siemens.com>,
"Burton, Ross" <ross.burton@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] libxml2: 2.9.4 -> 2.9.6
Date: Fri, 6 Oct 2017 16:59:34 +0300 [thread overview]
Message-ID: <2840d54c-8c0f-2ea0-2c81-6acd99953371@linux.intel.com> (raw)
In-Reply-To: <53132579-3c1a-7adb-bb13-4518d9ba3543@siemens.com>
On 10/06/2017 04:19 PM, Andrej Valek wrote:
> It is continue in discussion from thread
> (http://lists.openembedded.org/pipermail/openembedded-core/2017-September/142891.html).
>
> For the explanation CVE-* fx-* patches have been removed due to
> backports. Ptest patch has been modified to adapt new changes in sources.
What I meant is that you need to put this information into the commit
message itself. Be generous with it; the more it contains, the better.
Alex
next prev parent reply other threads:[~2017-10-06 14:03 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
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 [this message]
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=2840d54c-8c0f-2ea0-2c81-6acd99953371@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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.