Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] update to udev-100
Date: Fri, 1 Dec 2006 18:57:56 +0100	[thread overview]
Message-ID: <20061201175756.GC27853@aon.at> (raw)
In-Reply-To: <20061201175030.GB27853@aon.at>

On Fri, Dec 01, 2006 at 06:50:30PM +0100, Bernhard Fischer wrote:
>On Wed, Nov 29, 2006 at 10:38:47PM +0100, Petr Stetiar wrote:
>>aldot at uclibc.org <aldot@uclibc.org> [2006-11-29 10:59:44]:
>>
>>> Author: aldot
>>> Date: 2006-11-29 10:59:43 -0800 (Wed, 29 Nov 2006)
>>> New Revision: 16723
>>> 
>>> Log:
>>> - build a udev for the target rather than for the host.
>>
>>Attached patch bumps version to 100, fixes Makefile and init script.
>
>I use busybox's mdev if i need someone to mknod under me, but ok.

Applied as r16746.
thanks,

PS: looking for the udev update bugs in the bug collector to clean 'em
out now..

  reply	other threads:[~2006-12-01 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 18:59 [Buildroot] svn commit: trunk/buildroot/package/udev aldot at uclibc.org
2006-11-29 21:38 ` Petr Stetiar
2006-12-01 17:50   ` Bernhard Fischer
2006-12-01 17:57     ` Bernhard Fischer [this message]
2006-12-01 20:47     ` ynezz

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=20061201175756.GC27853@aon.at \
    --to=rep.nop@aon.at \
    --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