All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: Paul Rolland <rol@as2917.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel .config support?
Date: Mon, 6 Jan 2003 10:02:19 -0500	[thread overview]
Message-ID: <20030106150219.GA22895@gnu.org> (raw)
In-Reply-To: <004701c2b553$57c0c780$3f00a8c0@witbe>

On Mon, Jan 06, 2003 at 08:15:07AM +0100, Paul Rolland wrote:
> > probability of a feature printing a copyright notice at init 
> > time is inversely proportional to its importance!]
>
> This can be removed too, in fact I don't care. I just put it because many
> others are doing so

That's the problem.... :-)

I understand why people do this -- it's nice to see your name pop up and get
a bit credit -- but really, there are simply too many people working on linux
for it to really make sense.

I wish someone with a bit of pull would go through and just trash the whole
lot, leaving just the printks that give actual useful information (and even
those could often do with quite a bit of pruning)...

[I'm too chicken to brave the flames that would probably result from trying]

-Miles
-- 
o The existentialist, not having a pillow, goes everywhere with the book by
  Sullivan, _I am going to spit on your graves_.

       reply	other threads:[~2003-01-06 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <buo3co7aujp.fsf@mcspd15.ucom.lsi.nec.co.jp>
     [not found] ` <004701c2b553$57c0c780$3f00a8c0@witbe>
2003-01-06 15:02   ` Miles Bader [this message]
2003-01-12 14:20     ` kernel .config support? Paul Rolland
2003-01-02 14:32 Robert P. J. Day
2003-01-02 15:43 ` Randy.Dunlap
2003-01-03  0:51   ` Randy.Dunlap
2003-01-02 17:11 ` Alan Cox
2003-01-02 16:43   ` Robert P. J. Day
2003-01-02 16:52     ` Khalid Aziz
2003-01-02 18:37       ` Paul Rolland
2003-01-02 23:22     ` Randy.Dunlap
2003-01-03  0:59 ` Erik Hensema

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=20030106150219.GA22895@gnu.org \
    --to=miles@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rol@as2917.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 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.