Thread (10 messages) 10 messages, 4 authors, 2024-02-15

Re: [PATCH] branch: rework the descriptions of rename and copy operations

From: Dragan Simic <hidden>
Date: 2024-02-15 23:09:34

On 2024-02-15 23:56, Kyle Lippincott wrote:
On Thu, Feb 15, 2024 at 2:38 PM Dragan Simic [off-list ref] 
wrote:
quoted
On 2024-02-15 23:31, Kyle Lippincott wrote:
quoted
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. :)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help