From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] X11 component versions
Date: Mon, 4 Feb 2013 21:40:18 +0100 [thread overview]
Message-ID: <20130204214018.2efc0bfb@skate> (raw)
In-Reply-To: <510F9768.4020907@carallon.com>
Will, Nicolas,
On Mon, 04 Feb 2013 11:11:36 +0000, Will Wagner wrote:
> You can find my work on updating to x11r7.7 on gitorious at
> https://gitorious.org/willw-buildroot/willw-buildroot/commits/remotes/gitorious/x11r7.7
>
> It is now based on a much older buildroot version and needs a lot of
> work to update.
Also you could look at the support/scripts/xorg-release script I added
some time ago. For each X.org component, it compares the version we
have in Buildroot with the version available in a certain X.org
release (currently X11R7.7).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-04 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 9:44 [Buildroot] X11 component versions Nicolas Dechesne
2013-02-04 10:45 ` Will Wagner
2013-02-04 10:56 ` Nicolas Dechesne
2013-02-04 11:11 ` Will Wagner
2013-02-04 20:40 ` Thomas Petazzoni [this message]
2013-02-04 20:49 ` Nicolas Dechesne
2013-02-04 21:30 ` Thomas Petazzoni
2013-02-04 21:37 ` Nicolas Dechesne
2013-02-04 22:06 ` Arnout Vandecappelle
2013-02-04 22:41 ` Nicolas Dechesne
2013-02-04 22:24 ` Thomas Petazzoni
2013-02-04 22:45 ` Nicolas Dechesne
2013-02-04 22:54 ` Thomas Petazzoni
2013-02-04 20:42 ` Nicolas Dechesne
2013-02-04 22:46 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 8:52 Jesper Birksø Bækdahl
2013-03-18 8:05 ` Arnout Vandecappelle
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=20130204214018.2efc0bfb@skate \
--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