From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/cairo: fix CVE-2018-19876
Date: Sun, 1 Mar 2020 17:27:31 +0100 [thread overview]
Message-ID: <20200301162731.GQ8743@scaer> (raw)
In-Reply-To: <87a750ysuq.fsf@tarshish>
Baruch, All,
On 2020-03-01 17:53 +0200, Baruch Siach spake thusly:
> On Sun, Mar 01 2020, Yann E. MORIN wrote:
> > On 2020-02-29 21:00 +0100, Fabrice Fontaine spake thusly:
> >> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> > As per Peter's review, this is a long shot for a security fix: better
> > backport the two patches (+autoreconf) for master. The version bump can
> > then be respun for next or after the merge.
> > I've marked this as chages-requested in patchwork.
> Are you sure? This patch is now master commit 91b150dc33841be1.
OK, I got super confussed, then:
- https://patchwork.ozlabs.org/patch/1247071/ wsa the security bump,
and the one I reviewed (and came to the same conclusion as Peter),
and which I marked as changes-requested;
- https://patchwork.ozlabs.org/patch/1247133/ is the one Peter
applied, and the mail I replied to with the conclusion of the bump,
above.
So, after shaking my head to put everything back in their places, I
marked 1247071 as enw again, while 1247133 was already marked accepted.
Damn... Thanks for noticing.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-03-01 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 20:00 [Buildroot] [PATCH 1/1] package/cairo: fix CVE-2018-19876 Fabrice Fontaine
2020-02-29 22:16 ` Peter Korsgaard
2020-03-01 15:42 ` Yann E. MORIN
2020-03-01 15:53 ` Baruch Siach
2020-03-01 16:21 ` Yann E. MORIN
2020-03-01 16:27 ` Yann E. MORIN [this message]
2020-03-14 18:09 ` Peter Korsgaard
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=20200301162731.GQ8743@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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