From: Lampshade <lampshade@poczta.fm>
To: intel-gfx@lists.freedesktop.org
Subject: [ANNOUNCE] xf86-video-intel 2.99.917
Date: Thu, 28 Jan 2016 09:06:28 +0100 [thread overview]
Message-ID: <blddjbtnmzikysxmqklb@sesw> (raw)
>>> However, as a couple of crashers
>>> slipped through into 2.99.916 (though not actual regressions in
>>> 2.99.916 per se) and 3 months have passed, we should make one more
>>> snapshot before an imminent release.
> Distributions are forced to randomly pick some git snapshot. Often it's
> not too much stuff broken. No stable release or branch we can rely on.
>
> Is Intel not able to maintain its own device driver in a usable way?
I also wonder what's going on.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-01-28 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:06 Lampshade [this message]
[not found] ` <widruunxaxmmvcqlyprq@clkp>
2016-02-01 16:33 ` [ANNOUNCE] xf86-video-intel 2.99.917 Lampshade
-- strict thread matches above, loose matches on Subject: below --
2014-12-21 14:47 Chris Wilson
2015-05-06 20:02 ` Julien Cristau
2016-01-26 18:03 ` Andreas Radke
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=blddjbtnmzikysxmqklb@sesw \
--to=lampshade@poczta.fm \
--cc=intel-gfx@lists.freedesktop.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