From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt
Date: Mon, 14 Apr 2008 08:07:01 -0700 [thread overview]
Message-ID: <48037315.6080305@oracle.com> (raw)
In-Reply-To: <28421.1208181120@vena.lwn.net>
Jonathan Corbet wrote:
> Dmitri Vorobiev <dmitri.vorobiev@gmail.com> wrote:
>
>> Offhand, it seems that the double spacing convention is being currently used
>> in a more or less consistent manner throughout Linux docs. It also seems to
>> me that this can be made a requirement and documented somewhere.
>
> Double spacing is my preference, and I appreciate your sending a new
> patch which doesn't take that out.
>
> But *please* let's not try to make "requirements" along those lines. If
> somebody's going to go to the trouble to write some documentation, I
> don't think we really want people bouncing it back to them with 100
> "single space after period" errors from checkpatch.pl...
Big Ack on that.
--
~Randy
next prev parent reply other threads:[~2008-04-14 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 18:26 [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt Dmitri Vorobiev
2008-04-13 22:10 ` Randy Dunlap
2008-04-13 22:25 ` Dmitri Vorobiev
2008-04-13 22:45 ` Al Viro
2008-04-13 22:49 ` Dmitri Vorobiev
2008-04-14 2:09 ` Randy Dunlap
2008-04-14 2:33 ` Dmitri Vorobiev
2008-04-14 13:52 ` Jonathan Corbet
2008-04-14 14:21 ` Dmitri Vorobiev
2008-04-14 15:07 ` Randy Dunlap [this message]
2008-04-14 15:13 ` Jan Engelhardt
2008-04-14 3:09 ` Al Viro
2008-04-13 23:55 ` Nick Andrew
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=48037315.6080305@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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