From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/RelNotes/2.51.0: improve wording for a couple entries
Date: Thu, 07 Aug 2025 08:46:35 -0700 [thread overview]
Message-ID: <xmqqfre3rv6s.fsf@gitster.g> (raw)
In-Reply-To: <20250807-pks-relnotes-2-51-fixes-v1-1-507fd15b28f4@pks.im> (Patrick Steinhardt's message of "Thu, 07 Aug 2025 07:09:25 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> Improve wording and fix typos for a couple entries part of the Git 2.51
> release notes.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
Thanks.
> Documentation/RelNotes/2.51.0.adoc | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/RelNotes/2.51.0.adoc b/Documentation/RelNotes/2.51.0.adoc
> index f8adc2c5cf..e2cd673f43 100644
> --- a/Documentation/RelNotes/2.51.0.adoc
> +++ b/Documentation/RelNotes/2.51.0.adoc
> @@ -97,8 +97,8 @@ Performance, Internal Implementation, Development Support etc.
> * "git push" and "git fetch" are taught to update refs in batches to
> gain performance.
>
> - * Some code paths in the "git prune" used to ignore passed in
> - repository object and used the_repository singleton instance
> + * Some code paths in "git prune" used to ignore the passed-in
> + repository object and used the `the_repository` singleton instance
> instead, which has been corrected.
>
> * Update ".clang-format" and ".editorconfig" to match our style guide
> @@ -139,7 +139,7 @@ Performance, Internal Implementation, Development Support etc.
> * Redefine where the multi-pack-index sits in the object subsystem,
> which recently was restructured to allow multiple backends that
> support a single object source that belongs to one repository. A
> - midx does span mulitple "object sources".
> + MIDX does span multiple "object sources".
>
> * Reduce implicit assumption and dependence on the_repository in the
> object-file subsystem.
> @@ -292,8 +292,8 @@ including security updates, are included in this release.
> and also they learn to honor the -U<n> command-line option.
> (merge 2b3ae04011 lm/add-p-context later to maint).
>
> - * The case where a new submodule takes a path where used to be a
> - completely different subproject is now dealt a bit better than
> + * The case where a new submodule takes a path where there used to be a
> + completely different subproject is now dealt with a bit better than
> before.
> (merge 5ed8c5b465 kj/renamed-submodule later to maint).
>
>
> ---
> base-commit: 64cbe5e2e8a7b0f92c780b210e602496bd5cad0f
> change-id: 20250807-pks-relnotes-2-51-fixes-0e72ed15c5bf
prev parent reply other threads:[~2025-08-07 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 5:09 [PATCH] Documentation/RelNotes/2.51.0: improve wording for a couple entries Patrick Steinhardt
2025-08-07 15:46 ` 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=xmqqfre3rv6s.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).