All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] config: fix some small capitalization issues, as spotted
Date: Sun, 31 Mar 2024 16:01:22 -0700	[thread overview]
Message-ID: <xmqq34s6f1kt.fsf@gitster.g> (raw)
In-Reply-To: <26135b06c48565ee8ac6dcfc1ef5431511e6202c.1711918168.git.dsimic@manjaro.org> (Dragan Simic's message of "Sun, 31 Mar 2024 22:49:30 +0200")

Dragan Simic <dsimic@manjaro.org> writes:

> Fix some small capitalization issues, as spotted while going through the
> documentation.  In general, a semicolon doesn't start a new sentence, and
> "this" has no meaning of a proper noun in this context.
>
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
> ---
>
> Notes:
>      * Fix some small capitalization issues in the documentation.

Thanks.

> diff --git a/Documentation/config/core.txt b/Documentation/config/core.txt
> index 2d4bbdb25fa3..41b071d8851c 100644
> --- a/Documentation/config/core.txt
> +++ b/Documentation/config/core.txt
> @@ -688,7 +688,7 @@ core.createObject::
>  	will not overwrite existing objects.
>  +
>  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.
>  
>  core.notesRef::

      reply	other threads:[~2024-03-31 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 20:49 [PATCH v2] config: fix some small capitalization issues, as spotted Dragan Simic
2024-03-31 23:01 ` Junio C Hamano [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=xmqq34s6f1kt.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 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.