From: Dragan Simic <dsimic@manjaro.org>
To: Kyle Lippincott <spectral@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] branch: rework the descriptions of rename and copy operations
Date: Fri, 16 Feb 2024 00:09:31 +0100 [thread overview]
Message-ID: <c1d8d7ec8639db564d09fd50ce9cf82a@manjaro.org> (raw)
In-Reply-To: <CAO_smVizZ6K-tSSubr7Pd95zn42GAHrgeeSQ7ZWmKdPH7gMy3w@mail.gmail.com>
On 2024-02-15 23:56, Kyle Lippincott wrote:
> On Thu, Feb 15, 2024 at 2:38 PM Dragan Simic <dsimic@manjaro.org>
> wrote:
>> On 2024-02-15 23:31, Kyle Lippincott wrote:
>> > Very minor nit: the prevailing style in this document appears to be to
>> > have a single space after the period, but it's definitely
>> > inconsistent. I don't see anything in Documentation/CodingGuidelines
>> > suggesting one way or the other, so don't consider this comment as
>> > blocking, just informational. If we want to achieve (eventual)
>> > consistency, we may want to use a single space after the period now.
>>
>> In this case, I went with following the intersentence spacing used in
>> the surrounding text. Though, my brain and muscle memory are kind of
>> hardcoded to use double spacing, which may not be as prevalent as a
>> while
>> ago, but IMHO makes reading text rendered using a fixed-width font
>> much
>> easier. I can adjust if needed, of course.
>
> No need to adjust if I'm the only one mentioning it. I'm very new to
> the project, so please don't take my style nits as any sort of
> mandate, since I'm the one that's most likely to be miscalibrated. :)
Basically, when it comes to the intersentence spacing, it seems that
double spacing has lost its popularity over time. It originates from
the old times when mechanical typewriters were used, which most people
probably don't even remember these days. :)
prev parent reply other threads:[~2024-02-15 23:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 18:42 [PATCH] branch: rework the descriptions of rename and copy operations Dragan Simic
2024-02-15 19:28 ` Kristoffer Haugsbakk
2024-02-15 19:47 ` Dragan Simic
2024-02-15 20:41 ` Junio C Hamano
2024-02-15 21:00 ` Dragan Simic
2024-02-15 21:52 ` Rubén Justo
2024-02-15 22:13 ` Junio C Hamano
2024-02-15 23:34 ` Rubén Justo
2024-02-16 3:32 ` Dragan Simic
2024-02-17 14:58 ` Rubén Justo
2024-02-18 20:38 ` Dragan Simic
2024-02-19 19:49 ` Junio C Hamano
2024-02-19 19:55 ` Dragan Simic
2024-02-20 18:24 ` Junio C Hamano
2024-02-20 19:12 ` Rubén Justo
2024-02-20 19:49 ` Dragan Simic
2024-02-20 20:25 ` [PATCH] branch: adjust documentation Rubén Justo
2024-02-20 20:34 ` Dragan Simic
2024-02-28 2:19 ` Dragan Simic
2024-02-28 17:20 ` Junio C Hamano
2024-02-28 17:24 ` Junio C Hamano
2024-02-29 1:56 ` Dragan Simic
2024-02-29 18:56 ` Rubén Justo
2024-02-29 19:33 ` Junio C Hamano
2024-02-29 20:02 ` Rubén Justo
2024-02-29 20:09 ` Dragan Simic
2024-03-02 16:18 ` Rubén Justo
2024-02-20 19:32 ` [PATCH] branch: rework the descriptions of rename and copy operations Dragan Simic
2024-02-20 19:14 ` Rubén Justo
2024-02-20 19:56 ` Dragan Simic
2024-02-15 22:27 ` Dragan Simic
2024-02-15 23:38 ` Rubén Justo
2024-02-15 22:31 ` Kyle Lippincott
2024-02-15 22:38 ` Dragan Simic
2024-02-15 22:56 ` Kyle Lippincott
2024-02-15 23:09 ` Dragan Simic [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=c1d8d7ec8639db564d09fd50ce9cf82a@manjaro.org \
--to=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=spectral@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).