mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Thu, 17 Nov 2005 13:54:22 +0000	[thread overview]
Message-ID: <20051117135421.GJ2193@spitz.ucw.cz> (raw)
In-Reply-To: <20051115055229.GA6163@kroah.com>

Hi!

> > Those who don't notice Documentation, don't deserve it, and are not
> > likely/willingly to be the audience,
> 
> Actually this is exactly the audience this is for, people who do not
> know where to look for the stuff they are trying to find.
> 
> Now getting people to realize that this is the file they really want to
> look at is a different task, but not impossible.
> 
> > > Now if those same people would notice anything in the root directory
> > > either, is another story...
> > 
> > That is rather like top-posting or CAPITALIZATION, or spamming.
> 
> Cool, I'm a top-poster, SPAMMER for creating a HOWTO file in the root
> directory of the kernel tree.  And here I thought I had been called
> every bad name in the book before :)

HOWTO is really wrong name for it. I'd expect "how to compile kernel" there.
Plus, some people actually needing advice will miss it because they'll only
search Doc*/

-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


  parent reply	other threads:[~2005-11-18 23:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:07 Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43   ` [RFC] [HUMOR] " Jeffrey V. Merkey
2005-11-15  0:18   ` [RFC] " Kalin KOZHUHAROV
2005-11-15  0:32     ` Randy.Dunlap
2005-11-15  4:58     ` Greg KH
2005-11-15  8:37       ` Paolo Ciarrocchi
2005-11-15 19:04         ` Greg KH
2005-11-15  0:32   ` Josh Boyer
2005-11-15  1:25     ` Paul Jackson
2005-11-15  1:31       ` Randy.Dunlap
2005-11-15  2:16       ` Josh Boyer
2005-11-15  2:42         ` Paul Jackson
2005-11-15  2:52           ` Josh Boyer
2005-11-15  3:01             ` Paul Jackson
2005-11-15  4:48               ` Greg KH
2005-11-15  4:47             ` Greg KH
2005-11-15  1:08 ` Coywolf Qi Hunt
2005-11-15  4:38   ` Greg KH
2005-11-15  5:51     ` Coywolf Qi Hunt
2005-11-15  5:52       ` Greg KH
2005-11-15  6:31         ` Coywolf Qi Hunt
2005-11-17 13:54         ` Pavel Machek [this message]
2005-11-15 14:42 ` Andi Kleen
2005-11-15 17:33   ` Greg KH
2005-11-16  8:12     ` Michael Kerrisk
2005-11-17  6:56       ` Greg KH
2005-11-17 12:12         ` Michael Kerrisk
2005-11-15 20:10 ` Luca
2005-11-15 20:13   ` Josh Boyer
2005-11-15 20:56   ` Greg KH
2005-11-16  4:38     ` Randy.Dunlap
2005-11-15 22:20   ` sitexec
2005-11-16 12:15 linux

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=20051117135421.GJ2193@spitz.ucw.cz \
    --to=pavel@suse.cz \
    --cc=coywolf@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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

all inboxes | Powered by JetHome®