From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] s/udev/mdev, how to proceed?
Date: Sun, 04 Dec 2011 12:27:57 -0500 [thread overview]
Message-ID: <4EDBAD9D.2040401@gentoo.org> (raw)
In-Reply-To: <CAA2qdGWQxmLJpErFNdXURaMTeo2s3tavZLk4PnhpKOibb2C6oA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On 12/04/2011 07:50 AM, Pandu Poluan wrote:
> First of all, apologies if I'm misusing this list. But I -- well, some
> Gentoo users, actually -- would really like to replace udev with mdev.
>
> We're currently fixing the complete procedure to do that, and when all
> show-stopping bugs have been ironed out, would like mdev to be an option
> for those who no longer want to be held hostage by the whims of udev
> upstream.
>
> We'd very much appreciate any guidance on how to proceed, like who to
> contact, what to submit, etc.
It sounds like you're going about it in the right way.
I'm guessing you are going to run into issues with desktop-y packages.
If you can provide sane fixes or workarounds for these issues, please
file bugs with patches.
Basically, as long as your changes don't break anything and aren't
horribly ugly, I don't think you'll have too much trouble convincing
package maintainers to apply them.
You may have a harder time convincing the docs team to put it in
official documentation (like the handbook). I would suggest using the
new wiki[1] to write a how-to or something.
[1] http://wiki.gentoo.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
prev parent reply other threads:[~2011-12-04 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 12:50 [gentoo-project] s/udev/mdev, how to proceed? Pandu Poluan
2011-12-04 17:27 ` Mike Gilbert [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=4EDBAD9D.2040401@gentoo.org \
--to=floppym@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/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