From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] udev: bump version to 164, add optional support for all extras, depend on host-gperf
Date: Thu, 20 Jan 2011 13:25:09 -0300 [thread overview]
Message-ID: <4D3861E5.6080400@zacarias.com.ar> (raw)
In-Reply-To: <4D33D762.4010502@ethertek.ca>
On 01/17/11 02:45, Dan Pattison wrote:
> Hello,
>
> I would like your udev support patches for uclibc-0.9.30.1 please, so I
> could use a newer udev.
>
> Thank you,
>
> Dan Pattison
Try to keep replies on the list.
From a quick test the same patches apply to 0.9.30.3, so they should
probably apply to 0.9.30.1 too.
If it works and other things aren't missing from the 0.9.30 series is
completely unknown to me, i have no need to stick with old versions.
Buildroot-wise 0.9.32 will probably be out soon (-rc2 out today) so
there really isn't much interest in backporting things for 0.9.30.
Regards.
prev parent reply other threads:[~2011-01-20 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 15:24 [Buildroot] [PATCH v3] udev: bump version to 164, add optional support for all extras, depend on host-gperf heiko at zuerker.org
2011-01-12 19:00 ` Gustavo Zacarias
[not found] ` <4D33D762.4010502@ethertek.ca>
2011-01-20 16:25 ` Gustavo Zacarias [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=4D3861E5.6080400@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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