From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion for easier bumping of Xorg packages
Date: Fri, 5 Aug 2011 16:56:26 +0200 [thread overview]
Message-ID: <20110805165626.26bd3b02@skate> (raw)
In-Reply-To: <20110805145820.3bbf8170@gmail.com>
Le Fri, 5 Aug 2011 14:58:20 +0200,
Frederic Bassaler <frederic.bassaler@gmail.com> a ?crit :
> What about reorganizing the package/x11r7 subdir?
>
> ie. instead of having everything in the same directory :
>
> xapp_xxx
> ...
> xdriver_xxxx
> ...
> xfont_xxx
>
> maybe it could be clearer to have the same subdirs as the
> http://xorg.freedesktop.org/releases/individual/ tree
Yeah, why not, but...
> so that we can bump up versions easier? (one subdirectory after
> another since there are many packages)
... what does this change to the problem of bumping the packages?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-08-05 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 12:58 [Buildroot] Suggestion for easier bumping of Xorg packages Frederic Bassaler
2011-08-05 14:56 ` Thomas Petazzoni [this message]
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=20110805165626.26bd3b02@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