linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Martin Kepplinger <martink@posteo.de>
Cc: mchehab@kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: Find more sane first words we have to say about Linux
Date: Mon, 1 May 2017 09:24:40 -0600	[thread overview]
Message-ID: <20170501092440.58c28368@lwn.net> (raw)
In-Reply-To: <20170430201135.11603-1-martink@posteo.de>

On Sun, 30 Apr 2017 22:11:35 +0200
Martin Kepplinger <martink@posteo.de> wrote:

> Imagine you're completely new to Linux, just real quick, ok? What do you do?
> Wouldn't having a look at README be under first if no *the* first thing?
> Ah there it is: README. "Linux kernel". nice! So what's that?
> "This file was moved to ...... Please notice that there are several....".
> Wtf!? Why? Can't they just tell me what's going on like a normal person?

So I don't doubt we could put something better there, but can we think for
a moment about who the audience is here?  If you're "completely new to
Linux", will you really start by jumping into the kernel source tree?
Somehow I'm not quite convinced...  It seems to me that the README file
should be aimed at developers who know what the kernel is but are not yet
familiar with the process of configuring and building it.

Thanks,

jon

  reply	other threads:[~2017-05-01 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 20:11 [PATCH] README: Find more sane first words we have to say about Linux Martin Kepplinger
2017-05-01 15:24 ` Jonathan Corbet [this message]
2017-05-01 16:01   ` Martin Kepplinger

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=20170501092440.58c28368@lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=mchehab@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).