From: Matt Turner <mattst88@gentoo.org>
To: Jeroen Roovers <jer@gentoo.org>
Cc: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Last rites: =x11-drivers/nvidia-drivers-375* =x11-drivers/nvidia-drivers-378* =x11-drivers/nvidia-drivers-381* =x11-drivers/nvidia-drivers-384* =x11-drivers/nvidia-drivers-387* =x11-drivers/nvidia-drivers-396*
Date: Mon, 17 Dec 2018 12:25:19 -0500 [thread overview]
Message-ID: <CAEdQ38E6uHDNMKkeU_r+Gm68iMqEXzUSpfL4Jz2DrOX=B-d6hg@mail.gmail.com> (raw)
In-Reply-To: <20181216232052.2a9a995f@wim.jer>
On Sun, Dec 16, 2018 at 5:20 PM Jeroen Roovers <jer@gentoo.org> wrote:
>
> On Sun, 16 Dec 2018 14:45:11 -0500
> Matt Turner <mattst88@gentoo.org> wrote:
>
> > I guess my question to you is whether you think it's okay to mask -304
> > for removal or whether there are enough users that we should keep it
> > under package.mask?
>
> "The Linux 304.* legacy driver series is the last to support the NV4x
> and G7x GPUs and motherboard chipsets based on them. Support for new
> Linux kernels and X servers, as well as fixes for critical bugs, will
> be included in 304.* legacy releases through the end of 2017." [1]
>
> That should be fine, then: 304 no longer receives security support so it
> can go away along with xorg-server-1.19.
Thanks Jer!
next prev parent reply other threads:[~2018-12-17 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 14:04 [gentoo-dev] Last rites: =x11-drivers/nvidia-drivers-375* =x11-drivers/nvidia-drivers-378* =x11-drivers/nvidia-drivers-381* =x11-drivers/nvidia-drivers-384* =x11-drivers/nvidia-drivers-387* =x11-drivers/nvidia-drivers-396* Jeroen Roovers
2018-12-14 20:03 ` Matt Turner
2018-12-16 19:40 ` Jeroen Roovers
2018-12-16 19:45 ` Matt Turner
2018-12-16 21:12 ` Mart Raudsepp
2018-12-16 21:54 ` Jeroen Roovers
2018-12-16 22:20 ` Jeroen Roovers
2018-12-17 17:25 ` Matt Turner [this message]
2018-12-15 8:53 ` Kent Fredric
2018-12-16 19:41 ` Jeroen Roovers
2018-12-16 22:14 ` Kent Fredric
2018-12-16 22:32 ` [gentoo-dev] " Jeroen Roovers
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='CAEdQ38E6uHDNMKkeU_r+Gm68iMqEXzUSpfL4Jz2DrOX=B-d6hg@mail.gmail.com' \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=jer@gentoo.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