public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] With regard to udev stabilization
Date: Wed, 14 Nov 2012 13:15:29 -0600	[thread overview]
Message-ID: <20121114191529.GA18138@linux1> (raw)
In-Reply-To: <CAB9SyzS6TFpKqFnEj0n3GVST96rkYkn2exDhrymkAUGrb9X6sQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

On Wed, Nov 14, 2012 at 05:07:26PM +0800, Ben de Groot wrote:
> On 13 November 2012 10:40, Richard Yao <ryao@gentoo.org> wrote:
> 
> > Dear Everyone,
> >
> > It is no secret that many of us are unhappy with the direction that udev
> > has taken under the leadership of the systemd developers. That includes
> > Linus Torvalds, who is 'leery of the fact that the udev maintenance
> > seems to have gone into some "crazy mode" where they have made changes
> > that were known to be problematic, and are pure and utter stupidity.'
> >
> > https://lkml.org/lkml/2012/10/2/505
> >
> > After speaking with several other Gentoo developers that share Linus'
> > concerns, I have decided to form a team to fork udev. Our plan is to
> > eliminate the separate /usr requirement from our fork, among other
> > things. We will announce the project later this week.
> >
> 
> 
> I applaud this initiative. I would recommend you contact, and try to work
> together with, the existing fork of udev, which is available in layman's
> udev overlay. There is a corresponding thread on our forums.

I already tried to open a dialog with these guys; they seem pretty
hostile; another "our way or the highway" approach seemed to be going on
there [1].

William

[1] https://bugs.gentoo.org/437570

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-11-14 21:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  2:40 [gentoo-project] With regard to udev stabilization Richard Yao
2012-11-13  3:22 ` Rich Freeman
2012-11-13  7:55 ` Fabian Groffen
2012-11-13 14:06   ` Rich Freeman
2012-11-13 15:44     ` Fabian Groffen
2012-11-13 15:46       ` Ian Stakenvicius
2012-11-13 15:48       ` Alexis Ballier
2012-11-13 18:08         ` Fabian Groffen
2012-11-13 18:40           ` Ian Stakenvicius
2012-11-13 19:12             ` Rich Freeman
2012-11-13 20:04     ` Pacho Ramos
2012-11-13 20:42       ` Tony "Chainsaw" Vroon
2012-11-13 21:17         ` Rich Freeman
2012-11-13  9:31 ` Markos Chandras
2012-11-13 11:26   ` Anthony G. Basile
2012-11-13 12:07     ` Markos Chandras
2012-11-13 13:16       ` Anthony G. Basile
2012-11-13 11:49   ` Pandu Poluan
2012-11-13 13:27     ` Richard Yao
2012-11-13 15:08       ` Markos Chandras
2012-11-13 16:01         ` Pandu Poluan
2012-11-14  6:42 ` Samuli Suominen
2012-11-14  9:12   ` Fabian Groffen
2012-11-14 11:13     ` Rich Freeman
2012-11-14  9:07 ` Ben de Groot
2012-11-14  9:44   ` Pandu Poluan
2012-11-14 19:15   ` William Hubbs [this message]
2012-11-14 19:52     ` Pandu Poluan
2012-11-15  9:13     ` Markos Chandras

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=20121114191529.GA18138@linux1 \
    --to=williamh@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