From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 10/12] package/x11r7/xserver_xorg-server: bump version to 1.18.0
Date: Sat, 19 Dec 2015 15:14:50 +0100 [thread overview]
Message-ID: <20151219151450.4ff3680a@free-electrons.com> (raw)
In-Reply-To: <567565C0.4090902@mind.be>
Arnout,
On Sat, 19 Dec 2015 15:12:16 +0100, Arnout Vandecappelle wrote:
> I would normally say that we should still have legacy handling here, to draw
> people's attention to the fact that something in the .config changed. However,
> it's just a change of version, and versions are changing all over the place, so
> indeed legacy handling isn't needed here.
As you say, we're bumping versions of tons of packages all the time,
without notifying users each time (it would be horrible), so why should
we do it specifically for the X.org server ? Especially when the user
has chosen to use the "tip" (1.17) and we're just updating to the more
recent "tip".
If we were to remove the 1.14 version, which is kept so far only for
compatibility with old NVidia X.org drivers, then maybe we should do
legacy handling (and even I'm not sure, because if we are to remove
this version, it means that we would have upgraded the NVidia drivers
to a version that works fine with a more recent X.org server).
Too much legacy handling is not good IMO.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-19 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 11:01 [Buildroot] [PATCH 01/12] package/apache: bump version to 2.4.18 Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 02/12] package/{mesa3d, mesa3d-headers}: bump version to 11.1.0 Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 03/12] package/mesa3d: add support for new virgl Gallium driver Bernd Kuhls
2015-12-19 21:48 ` Yann E. MORIN
2015-12-20 17:01 ` Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 04/12] package/mesa3d: add support for Nouveau DRI driver Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 05/12] package/libva: bump version to 1.6.2 Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 06/12] package/libva-intel-driver: " Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 07/12] package/nvidia-driver: bump version to 358.16 Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 08/12] package/x11r7/xdriver_xf86-video-ati: bump version to 7.6.1 Bernd Kuhls
2015-12-19 13:14 ` Thomas Petazzoni
2015-12-19 11:01 ` [Buildroot] [PATCH 09/12] package/x11r7/xdriver_xf86-video-intel: bump version Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 10/12] package/x11r7/xserver_xorg-server: bump version to 1.18.0 Bernd Kuhls
2015-12-19 13:17 ` Thomas Petazzoni
2015-12-19 14:12 ` Arnout Vandecappelle
2015-12-19 14:14 ` Thomas Petazzoni [this message]
2015-12-19 11:01 ` [Buildroot] [PATCH 11/12] package/libinput: bump version to 1.1.2 Bernd Kuhls
2015-12-19 11:01 ` [Buildroot] [PATCH 12/12] package/x11r7/xdriver_xf86-video-nouveau: new package Bernd Kuhls
2015-12-19 13:13 ` [Buildroot] [PATCH 01/12] package/apache: bump version to 2.4.18 Thomas Petazzoni
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=20151219151450.4ff3680a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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