Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] legacy/xserver: add a legacy entry for xserver >= 1.19.0
Date: Sun,  8 Jan 2017 23:20:11 +0100	[thread overview]
Message-ID: <20170108222011.3839-2-romain.naour@gmail.com> (raw)
In-Reply-To: <20170108222011.3839-1-romain.naour@gmail.com>

The legacy entry was missing in commit [1].

[1] ec502ea8e4fec1e113b5f7c532809a05644a9fd4

Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
---
 Config.in.legacy | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Config.in.legacy b/Config.in.legacy
index 20445b8..8dfbbc8 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -145,6 +145,13 @@ endif
 ###############################################################################
 comment "Legacy options removed in 2017.02"
 
+config BR2_PACKAGE_XSERVER_XORG_SERVER_AIGLX
+	bool "xserver AIGLX Extension removed"
+	depends on !BR2_PACKAGE_XSERVER_XORG_SERVER_V_1_14 && !BR2_PACKAGE_XSERVER_XORG_SERVER_V_1_17
+	select BR2_LEGACY
+	help
+	  The xserver AIGLX Extension has been removed in 1.19.0 release.
+
 config BR2_PACKAGE_PERL_DB_FILE
 	bool "perl-db-file removed"
 	select BR2_LEGACY
-- 
2.9.3

  reply	other threads:[~2017-01-08 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 22:20 [Buildroot] [PATCH] DEVELOPERS: Add entry for upower Romain Naour
2017-01-08 22:20 ` Romain Naour [this message]
2017-01-24 10:33   ` [Buildroot] [PATCH] legacy/xserver: add a legacy entry for xserver >= 1.19.0 Thomas Petazzoni
2017-01-25 10:56     ` Arnout Vandecappelle
2017-01-25 19:29       ` Romain Naour
2017-01-26 10:38         ` Arnout Vandecappelle
2017-01-26 20:59       ` Yann E. MORIN
2017-01-26 22:06         ` Peter Korsgaard
2017-01-09  8:43 ` [Buildroot] [PATCH] DEVELOPERS: Add entry for upower Peter Korsgaard

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=20170108222011.3839-2-romain.naour@gmail.com \
    --to=romain.naour@gmail.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