From: Julian Lunz <git@jlunz.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: backport hotplug support
Date: Thu, 14 Jun 2012 17:59:33 +0200 [thread overview]
Message-ID: <20120614175933.1460d2f5@jdeb> (raw)
In-Reply-To: <4FD8C77B.6050600@carallon.com>
On Wed, 13 Jun 2012 18:01:47 +0100
Will Wagner <will_wagner@carallon.com> wrote:
> 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
>
Hello Will,
I did the same ~1 year ago for X11R7.6 (just for the components I
needed) and that went pretty easy, basically just updating
the version numbers.
A quick check revealed 19 patches in x11r7-meta package, they might
need some adjustement.
If you need any help for 7.7, please let me know.
Regards,
Julian
next prev parent reply other threads:[~2012-06-14 15:59 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
2012-06-14 5:56 ` Peter Korsgaard
2012-06-14 15:59 ` Julian Lunz [this message]
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=20120614175933.1460d2f5@jdeb \
--to=git@jlunz.de \
--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.