From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] config: fix some small capitalization issues, as spotted
Date: Sat, 30 Mar 2024 13:34:40 -0700 [thread overview]
Message-ID: <xmqqo7avlaqn.fsf@gitster.g> (raw)
In-Reply-To: <6f6f821fc090fb59f632fcdbd061154b897b1244.1711772691.git.dsimic@manjaro.org> (Dragan Simic's message of "Sat, 30 Mar 2024 05:26:31 +0100")
Dragan Simic <dsimic@manjaro.org> writes:
> On some file system/operating system combinations, this is unreliable.
> -Set this config setting to 'rename' there; However, This will remove the
> +Set this config setting to 'rename' there; however, this will remove the
> check that makes sure that existing object files will not get overwritten.
Looking good, except that we do not want double-space after a
semicolon.
next prev parent reply other threads:[~2024-03-30 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 4:26 [PATCH] config: fix some small capitalization issues, as spotted Dragan Simic
2024-03-30 20:34 ` Junio C Hamano [this message]
2024-03-31 20:21 ` Dragan Simic
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=xmqqo7avlaqn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).