From: "Philip Oakley" <philipoakley@iee.org>
To: "Stefan Beller" <sbeller@google.com>,
"Kaartic Sivaraam" <kaarticsivaraam91196@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] doc: fix small issues in SubmittingPatches
Date: Tue, 1 Aug 2017 22:04:57 +0100 [thread overview]
Message-ID: <C89BA7B590AA460BB298258BA85E8619@PhilipOakley> (raw)
In-Reply-To: CAGZ79kYg9jQ3kaKnNEJCH9fde=ar1KPiUr7=X+TguNc0Twqdzg@mail.gmail.com
From: "Stefan Beller" <sbeller@google.com>
>> Further, remove duplicated space character.
>
> https://en.wikipedia.org/wiki/Sentence_spacing
> seems like a globally controversial thing. (I assumed
> it was some sort of local dialect before researching
> it properly)
>
> I personally do not mind one way or another regarding
> (double) spaces after a period, but I would think we'd
> strive for consistency throughout the project.
>
The use of double spaces was a taught typing technique as recently as the
early-mid 1980s when my wife did a UK university postgraduate secretarial
course. This was just before PC word processing took off. It takes a long
while for the old ways to die off!
--
Philip
prev parent reply other threads:[~2017-08-01 21:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 11:09 [PATCH 1/2] doc: fix small issues in SubmittingPatches Kaartic Sivaraam
2017-07-30 11:09 ` [PATCH 2/2] doc: add another way to identify if a patch has been merged Kaartic Sivaraam
2017-07-30 14:49 ` [PATCH 1/2] doc: fix small issues in SubmittingPatches Philip Oakley
2017-07-30 16:17 ` Kaartic Sivaraam
2017-07-30 16:18 ` Kaartic Sivaraam
2017-07-31 20:23 ` Stefan Beller
2017-07-31 20:34 ` Junio C Hamano
2017-08-01 15:59 ` Kaartic Sivaraam
2017-08-01 17:38 ` Stefan Beller
2017-08-02 12:22 ` [RFC] The correct and consistent alternative to quote a command ? Kaartic Sivaraam
2017-08-02 15:37 ` Junio C Hamano
2017-08-02 17:32 ` Stefan Beller
2017-08-03 15:35 ` Kaartic Sivaraam
2017-08-01 16:05 ` [PATCH 1/2] doc: fix small issues in SubmittingPatches Kaartic Sivaraam
2017-08-01 16:05 ` [PATCH 2/2] doc: add another way to identify if a patch has been merged Kaartic Sivaraam
2017-08-01 17:46 ` Stefan Beller
2017-08-02 12:32 ` Kaartic Sivaraam
2017-08-02 16:01 ` Junio C Hamano
2017-08-02 16:28 ` Junio C Hamano
2017-08-02 17:58 ` Stefan Beller
2017-08-07 14:34 ` Kaartic Sivaraam
2017-08-07 14:33 ` Kaartic Sivaraam
2017-08-01 21:04 ` Philip Oakley [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=C89BA7B590AA460BB298258BA85E8619@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaarticsivaraam91196@gmail.com \
--cc=sbeller@google.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.