Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: backport hotplug support
Date: Wed, 13 Jun 2012 18:01:47 +0100	[thread overview]
Message-ID: <4FD8C77B.6050600@carallon.com> (raw)
In-Reply-To: <20120613182859.3217c88c@skate>

On 13/06/2012 17:28, Thomas Petazzoni wrote:
>
> Unless I'm wrong X11R7.7 has been released some time ago, and it
> includes X server 1.12, at
> http://www.x.org/releases/X11R7.7/src/xserver/. So why would we bother
> backporting 1.8 material to a 1.7 version? Upgrading the complete X.org
> stack to X11R7.7 seems like a much more appropriate solution. Or maybe
> I'm missing something obvious?
>

I have largely finished ported over to 7.7 and hopefully will send some 
patches soon. I actually did the work a few months before the release so 
I need to go back and check package versions and also I have not tested 
that many packages yet.

Regards
Will

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  parent reply	other threads:[~2012-06-13 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 16:08 [Buildroot] [PATCH] xserver_xorg-server: backport hotplug support Richard Braun
2012-06-13 16:28 ` Thomas Petazzoni
2012-06-13 16:44   ` Richard Braun
2012-06-13 17:01   ` Will Wagner [this message]
2012-06-14  5:56     ` Peter Korsgaard
2012-06-14 15:59     ` Julian Lunz
2012-06-14  5:55   ` 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=4FD8C77B.6050600@carallon.com \
    --to=will_wagner@carallon.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