All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: akpm@linux-foundation.org, corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt
Date: Mon, 14 Apr 2008 02:25:05 +0400	[thread overview]
Message-ID: <48028841.900@gmail.com> (raw)
In-Reply-To: <20080413151020.bfa62f58.randy.dunlap@oracle.com>

Randy Dunlap пишет:
> On Sun, 13 Apr 2008 22:26:41 +0400 Dmitri Vorobiev wrote:
> 
>> A couple of typos crept into the newly added document
>> about the seq_file interface. This patch corrects those
>> typos and simultaneously deletes a few superfluous blanks.
> 
> The "2 spaces after a period at the end of a sentence" was done
> on purpose, I feel sure.  It's not a mistake.

OK, I'll redo the changes.

Actually, I was doubting whether the "2 spaces" thing was
intentional or not. The overwhelming majority of the sentences in
this document use only one space after a period, however, and this
made me decide that the "2 spaces" thing had not been deliberate
but just a typo.

Are there any rules about using spaces after a period at the end
of a sentence?

Thanks,
Dmitri

  reply	other threads:[~2008-04-13 22:25 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 [this message]
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
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=48028841.900@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 \
    /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.