public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] devfs is dead, let's move on
Date: Fri, 08 Jul 2005 20:36:53 +0200	[thread overview]
Message-ID: <1120847813.27435.44.camel@lycan.lan> (raw)
In-Reply-To: <20050708191631.24ddff4c@localhost>

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

On Fri, 2005-07-08 at 19:16 +0100, Stephen Bennett wrote:
> On Fri, 8 Jul 2005 10:06:45 -0700
> Greg KH <gregkh@gentoo.org> wrote:
> 
> > Heh, yes.  While looking in there, I was wondering if anyone would
> > object to splitting the udev and devfs stuff out of the main rc
> > script, like other parts have been split out?  That way I could
> > bundle the udev portions in the udev package and then keep them up to
> > date (like the "save modified device nodes logic") ?
> 
> I've been trying to get spanky to do this for a while now. If you
> could help annoy him enough that he actually does it I would be happy.

If I remember correctly, you had to show your updated /sbin/rc first so
that we could see what is duplicate and what not :P


-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-08 18:37 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 22:46 [gentoo-dev] devfs is dead, let's move on Greg KH
2005-07-06 23:04 ` Greg KH
2005-07-06 23:06 ` Roy Marples
2005-07-06 23:16   ` Greg KH
2005-07-07  0:35   ` Mike Frysinger
2005-07-07  9:34 ` Henrik Brix Andersen
2005-07-07 13:55 ` Martin Schlemmer
2005-07-07 19:44   ` [gentoo-dev] " Duncan
2005-07-07 20:06     ` Martin Schlemmer
2005-07-07 20:19       ` [gentoo-dev] " Duncan
2005-07-07 20:52   ` [gentoo-dev] " Greg KH
2005-07-07 23:22     ` Martin Schlemmer
2005-07-08 17:06       ` Greg KH
2005-07-08 18:16         ` Stephen Bennett
2005-07-08 18:36           ` Martin Schlemmer [this message]
2005-07-08 18:43         ` Martin Schlemmer
2005-07-07 14:18 ` Chris Gianelloni
2005-07-08 17:12   ` Greg KH
2005-07-09  1:00     ` Georgi Georgiev
2005-07-09  2:31       ` Greg KH
2005-08-01 22:14     ` Greg KH
2005-08-01 23:23       ` Kumba
2005-08-01 23:32         ` Greg KH
2005-08-01 23:40           ` Kumba
2005-08-01 23:56             ` Greg KH
2005-07-07 17:39 ` Georgi Georgiev
2005-07-08 17:15   ` Greg KH
2005-07-07 19:52 ` John Mylchreest
2005-07-07 20:49   ` Greg KH
2005-07-09  3:56   ` Kumba
2005-07-09  4:42     ` Greg KH
2005-07-09  5:22       ` Kumba
2005-07-08 17:49 ` Michiel de Bruijne
2005-07-08 22:25   ` Greg KH
2005-07-08 22:46     ` Michiel de Bruijne
2005-07-08 23:35     ` Martin Schlemmer
2005-07-09  0:44       ` Michiel de Bruijne
2005-07-09  0:58         ` Martin Schlemmer
2005-07-09  2:28       ` Greg KH
2005-07-09 18:34       ` Richard Fish
2005-07-09 18:50         ` Philippe Trottier
2005-07-11  7:47         ` Martin Schlemmer
2005-07-12 22:08           ` Mike Frysinger
2005-07-13  9:00             ` Martin Schlemmer
2005-07-13 12:55               ` Mike Frysinger
2005-07-13 14:44             ` Richard Fish
2005-07-15 23:37 ` Carlos Silva
2005-07-17 13:24   ` Greg KH

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=1120847813.27435.44.camel@lycan.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@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