From: "Jan Beulich" <JBeulich@suse.com>
To: Marek Marczykowski <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Backports to stable
Date: Mon, 08 Oct 2018 05:57:48 -0600 [thread overview]
Message-ID: <5BBB463C02000078001EF89A@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20181008104028.GA1645@mail-itl>
>>> On 08.10.18 at 12:40, <marmarek@invisiblethingslab.com> wrote:
> On Mon, Oct 08, 2018 at 03:29:06AM -0600, Jan Beulich wrote:
>> >>> On 07.10.18 at 03:04, <marmarek@invisiblethingslab.com> wrote:
>> > I'd like to propose backporting GCC7/8 fixes to all stable branches. Below
>> > is a list up to stable-4.6, but some of the patches are already on
>> > select branches (developed during that release cycle, or already
>> > backported).
>>
>> I continue to be opposed to backporting anything that is not needed
>> for dealing security issues to branches which are in security-support-
>> only mode, i.e. anything older than 4.8 at this point in time.
>
> Ok, noted. It's hard to compile those still security-supported versions
> on recent systems. But if one need such combination (old Xen + new other
> things), then can also apply those patches locally. I just wanted to
> reduce work duplication.
>
>> Furthermore I notice that 4.6 has just moved out of security support,
>> at the end of last week.
>
> Hmm, 18+18 months from October 13, 2015 is at the end of this week.
Quite possible - I'm not judging by announcement date, but by the
time stamp of xen/Makefile (which is always the last thing to get
updated, for the version adjustment).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-10-08 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 1:04 Backports to stable Marek Marczykowski-Górecki
2018-10-08 9:29 ` Jan Beulich
2018-10-08 10:40 ` Marek Marczykowski
2018-10-08 11:57 ` Jan Beulich [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=5BBB463C02000078001EF89A@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xenproject.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.