From: Pratyush Yadav <me@yadavpratyush.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Shourya Shukla <shouryashukla.oo@gmail.com>,
git@vger.kernel.org, sandals@crustytoothpaste.net,
emilyshaffer@google.com, martin.agren@gmail.com
Subject: Re: [PATCH 1/2] gitfaq: cleanup gitfaq.txt
Date: Wed, 8 Apr 2020 23:52:47 +0530 [thread overview]
Message-ID: <20200408182247.jz5xnlw3sbrazq36@yadavpratyush.com> (raw)
In-Reply-To: <xmqqy2r8tbxn.fsf@gitster.c.googlers.com>
On 06/04/20 04:46PM, Junio C Hamano wrote:
> Shourya Shukla <shouryashukla.oo@gmail.com> writes:
>
> By the way, if you still want to pursue "full-stop at the end of the
> sentence MUST be followed by no more than one SP", I won't stop you,
> but please do so in a separate patch that has NO OTHER CHANGES.
> They drown other changes out that are not mechanical and makes them
> hard to review.
Maybe we should just have a consistent convention throughout the
documentation on whether to use one space after a full-stop or two.
Right now in some places we use one space, in some others we use two,
even in the same file. This is slightly distracting when reading. Having
a convention would at least result in uniformity, even if it won't end
the debate on which is better. And FWIW, our man pages are always
rendered with one space, even if the source file has two.
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2020-04-08 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 18:12 [PATCH 0/2] Add more issues in gitfaq Shourya Shukla
2020-04-06 18:12 ` [PATCH 1/2] gitfaq: cleanup gitfaq.txt Shourya Shukla
2020-04-06 19:06 ` Junio C Hamano
2020-04-06 23:46 ` Junio C Hamano
2020-04-07 1:07 ` brian m. carlson
2020-04-07 3:15 ` Junio C Hamano
2020-04-08 18:22 ` Pratyush Yadav [this message]
2020-04-10 18:29 ` Junio C Hamano
2020-04-06 18:12 ` [PATCH 2/2] gitfaq: append the 'Common Issues' section Shourya Shukla
2020-04-06 19:28 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200408182247.jz5xnlw3sbrazq36@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=shouryashukla.oo@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).