All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: David Lang <david.lang@digitalinsight.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.13
Date: Sat, 10 Sep 2005 20:07:26 -0700	[thread overview]
Message-ID: <20050911030726.GA20462@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0509101742300.28852@qynat.qvtvafvgr.pbz>

On Sat, Sep 10, 2005 at 05:48:05PM -0700, David Lang wrote:
> On Fri, 9 Sep 2005, Greg KH wrote:
> 
> >Date: Fri, 9 Sep 2005 14:45:42 -0700
> >From: Greg KH <gregkh@suse.de>
> >To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
> >Cc: linux-kernel@vger.kernel.org
> >Subject: [GIT PATCH] Remove devfs from 2.6.13
> >
> >Here are the same "delete devfs" patches that I submitted for 2.6.12.
> >It rips out all of devfs from the kernel and ends up saving a lot of
> >space.  Since 2.6.13 came out, I have seen no complaints about the fact
> >that devfs was not able to be enabled anymore, and in fact, a lot of
> >different subsystems have already been deleting devfs support for a
> >while now, with apparently no complaints (due to the lack of users.)
> 
> do you really think that there have been that many people who have shifted 
> to 2.6.13 in less then 2 weeks since release?

Ok, how long should I wait then?

> I know that you take personal offense to this code existing, but Andrew 
> pointed out when you proposed these patches before that we need to be 
> acareful here

I know, that's fine.  But if I don't keep trying, how will it ever
happen?  :)

thanks,

greg k-h

  reply	other threads:[~2005-09-11  3:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 21:45 [GIT PATCH] Remove devfs from 2.6.13 Greg KH
2005-09-10  8:27 ` Mike Bell
2005-09-10 21:52   ` Greg KH
2005-09-10 23:03     ` Mike Bell
2005-09-11  5:09       ` Greg KH
2005-09-12 13:40         ` Steven Rostedt
2005-09-14 20:00         ` Mike Bell
2005-09-14 20:28           ` Kyle Moffett
2005-09-14 23:06           ` Greg KH
2005-09-15  2:10             ` Ioan Ionita
2005-09-10  9:03 ` [GIT PATCH] " Michael Thonke
2005-09-10 12:32   ` Douglas McNaught
2005-09-10 21:55   ` Greg KH
2005-09-10 14:15 ` J.A. Magallon
2005-09-10 23:24 ` J.A. Magallon
2005-09-10 23:30   ` Greg KH
2005-09-11  0:48 ` David Lang
2005-09-11  3:07   ` Greg KH [this message]
2005-09-11  6:08     ` David Lang
2005-09-11  7:05       ` Arjan van de Ven
2005-09-11  7:13       ` Valdis.Kletnieks
2005-09-11  7:20         ` David Lang
2005-09-11 11:02           ` Theodore Ts'o
2005-09-12  8:01             ` Martin Schlemmer
2005-09-11 17:15           ` Greg KH
2005-09-11 11:35         ` Bastian Blank
2005-09-11 11:42           ` CaT
2005-09-11 17:17       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2005-09-11 11:44 linux
2005-09-11 15:43 ` Kyle Moffett
2005-09-14 20:01   ` Mike Bell
2005-09-14 20:13     ` Kyle Moffett

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=20050911030726.GA20462@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.