mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: minor typo fixes in md.txt
Date: Mon, 31 Jul 2006 20:55:31 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0607311749570.8276@sheep.housecafe.de> (raw)
In-Reply-To: <20060731091155.5763dcc3.rdunlap@xenotime.net>

On Mon, 31 Jul 2006, Randy.Dunlap wrote:
> Attachments make review/feedback more difficult and less likely.

ACK, sorry.

> However, it is common (and hence not a problem) to use
> 2 spaces after a period (full stop) at the end of a sentence,
> so I would prefer that those parts of the patch be dropped.

Um, really? I've never seen this before...but then again I'm not a 
native english speaker, but I still find it annoying...hm, but that's no 
reason, right :-)

> -desipite possible corruption.  This is normally done with
> +desipite possible corruption. This is normally done with
> despite

ACK.

> Fix indentation/alignment.

The indentation of this file is...."interesting" and I did not dare to 
touch it, I thought it had some special meaning....

Anyway, I'll return to more important issues then, maybe Ingo just want 
to scratch one of the "level" explanations, this *is* confusing. But 
above all, I was really impressed to find all the sysfs-switches 
documented and now I know what this debian-checkarray script was up 
to...

Thanks,
Christian
-- 
BOFH excuse #198:

Post-it Note Sludge leaked into the monitor.

      reply	other threads:[~2006-07-31 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 12:02 Christian Kujau
2006-07-31 16:11 ` Randy.Dunlap
2006-07-31 19:55   ` Christian Kujau [this message]

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=Pine.LNX.4.64.0607311749570.8276@sheep.housecafe.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rdunlap@xenotime.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 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®