public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: linux-kernel@vger.kernel.org
Subject: Maybe I have a bad day or something
Date: Mon, 24 Dec 2001 15:07:51 -0200	[thread overview]
Message-ID: <01122415075100.02141@manta> (raw)

Hi all,

I'd like to share with all subscribers my experience with my first year on 
this list.

Posting questions here is fruitless. They are offtopic by definition.
Who fscking care that I am trying to debug a kernel problem and my first 
ksymoops compilation went astray? (I discovered that ksymoops needs bfd lib 
from binutils a month later). We need no stinking decoded oops!
And we never were newbies, we were born with Linux in our blood!

Well, maybe the list is useful for bug reports? Maybe, here is an example:
>> BTW, don't go for 2.4.x, x>10. initrd is broken there and is still unfixed.
>Bullshit.
I've done a damn good investigation on that, I compiled over a dozen kernels 
for that, I *know* where is the bug, I don't just moaning! Response: either 
deafening silence or this "warm and encouraging" reply. We need no stinking 
details of your problems.

You may think that this list is for patches. Well, partly.
Patches submitted here are ignored 50% of times. What's the use in explaining 
to poster why patch is bad and how to improve it? He's expected to read minds 
from distance. Or maybe we need no stinking new hackers, old boys are enough?

What this list is good for? I'll tell ya:

a) for discussions about proper name and abbreviation of kilobyte.
   Oh, now I know how many _true _coders_ are there!
   Just count that "KB/KiB" subj line in your lkml mail folder.

b) for telling patch authors that their patch should NOT be applied.
   ("Why we should turn off those bits in VIA chipset? They're documented
   as 'debug, dont touch'". Who cares that with those bits set to 1
   Athlons are oopsing like crazy.) It's so much easier to flame
   that to _make_ patches, isn't it?

Ok, enough. Steam pressure is much lower now :-)

I wish in 2002 lkml signal/noise ratio to be much higher.
How about putting that in standard lkml sig:

-To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
+Please make sure your posting is *useful* for linux kernel development
+To unsubscribe: read  http://vger.kernel.org/majordomo-info.html
 Please read the FAQ at  http://www.tux.org/lkml/

OTOH, I must say that there are quite some good people there
I want to say "Thank you! Great coding!" to:

Linus, Alan Cox, Marcelo Tosatti (kernel maintenance) 
  (what about bug/patch tracking system, leaders?
  it's sad to see good patches dropped and longstanding
  bugs unaddressed)
Andrea Arcangeli (VM)
Robert Love (preemption)
Richard Gooch (devfs)
Trond Myklebust (nfs)
Al Viro (fs)
  (but could you _please_ be less agressive Al? Your comments are useful,
  but your emotions are always negative! What we have done to you?)

I don't remember all of you, definitely this list must be longer...

Happy New Year to everyone.
--
vda

             reply	other threads:[~2001-12-24 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-24 17:07 vda [this message]
2001-12-24 14:23 ` Maybe I have a bad day or something Pat Villani
2001-12-24 16:11   ` Matthew Johnson
2001-12-24 17:39     ` David Lang
2001-12-24 18:21       ` John Alvord
2001-12-25 17:21   ` Matthew M
2001-12-24 15:27 ` Wakko Warner
2001-12-24 21:07 ` Stevie O
2001-12-24 22:18   ` Andreas Steinmetz
2001-12-25  8:09 ` Mike Galbraith
2001-12-25  9:30   ` Keith Owens
2001-12-31  1:13     ` Mark Harrop

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=01122415075100.02141@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=linux-kernel@vger.kernel.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