All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt
Date: Mon, 14 Apr 2008 18:21:46 +0400	[thread overview]
Message-ID: <4803687A.2060404@gmail.com> (raw)
In-Reply-To: <28421.1208181120@vena.lwn.net>

Jonathan Corbet пишет:
> 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...
> 

OK, clear enough. Thanks.

Dmitri

> Thanks,
> 
> jon
> 


  reply	other threads:[~2008-04-14 14:26 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 [this message]
2008-04-14 15:07             ` Randy Dunlap
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=4803687A.2060404@gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.