From: Arnout Vandecappelle <arnout@mind.be>
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:12:16 +0100 [thread overview]
Message-ID: <567565C0.4090902@mind.be> (raw)
In-Reply-To: <20151219141714.5da170a3@free-electrons.com>
On 19-12-15 14:17, Thomas Petazzoni wrote:
> Dear Bernd Kuhls,
>
> Adding Arnout in Cc, since he is our legacy handling expert :)
>
> On Sat, 19 Dec 2015 12:01:30 +0100, Bernd Kuhls wrote:
>> - added legacy handling for BR2_PACKAGE_XSERVER_XORG_SERVER_V_1_17
>
> Is this really needed? In any case, without legacy handling, the thing
> will automatically fall back to version 1.18, which is what we want. So
> I'm questioning whether legacy handling is needed.
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.
Regards,
Arnout
>
>> - legacy handling for BR2_PACKAGE_XSERVER_XORG_SERVER_VIDEODRV_ABI_19
>> is not needed because this option is not used by other packages
>
> BR2_PACKAGE_XSERVER_XORG_SERVER_VIDEODRV_ABI_19 is a blind option, so
> there is no point in adding legacy handling for it.
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-12-19 14:12 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 [this message]
2015-12-19 14:14 ` Thomas Petazzoni
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=567565C0.4090902@mind.be \
--to=arnout@mind.be \
--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 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.