public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: kristofferhaugsbakk@fastmail•com
Cc: git@vger•kernel.org,  Kristoffer Haugsbakk <code@khaugsbakk•name>
Subject: Re: [PATCH] RelNotes/2.50.0: fix typos & other improvements
Date: Wed, 11 Jun 2025 12:34:05 -0700	[thread overview]
Message-ID: <xmqq34c6hy36.fsf@gitster.g> (raw)
In-Reply-To: <d809e4bfdad2bedff66acaad81b3ea2290ae20ac.1749663244.git.code@khaugsbakk.name> (kristofferhaugsbakk@fastmail.com's message of "Wed, 11 Jun 2025 19:35:24 +0200")

kristofferhaugsbakk@fastmail•com writes:

> From: Kristoffer Haugsbakk <code@khaugsbakk•name>
>
> • Replace with phrases that are more standard (“all-or-nothing”
>   instead of “-none”)
> • Add coordinating words that make it less likely for you to trip
>   over the sentence (“*that* "gc" can do”)
> • Use “SMTP” instead of both SMTP and smtp
> • Don’t mention `git fsck --reference` since the previous release
>   was not affected by this minor bug.  Also say “errored out” since
>   the git-refs(1) bug was there in v2.48.0 as well
> • Use the more widespread “linked” instead of “secondary worktree”
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk•name>
> ---
>  Documentation/RelNotes/2.50.0.adoc | 17 ++++++++---------
>  1 file changed, 8 insertions(+), 9 deletions(-)

Thanks.

>
> diff --git a/Documentation/RelNotes/2.50.0.adoc b/Documentation/RelNotes/2.50.0.adoc
> index 99acf814875..2a1463644b4 100644
> --- a/Documentation/RelNotes/2.50.0.adoc
> +++ b/Documentation/RelNotes/2.50.0.adoc
> @@ -36,7 +36,7 @@ UI, Workflows & Features
>   * Auth-related (and unrelated) error handling in send-email has been
>     made more robust.
>  
> - * Updating multiple references have only been possible in all-or-none
> + * Updating multiple references have only been possible in an all-or-nothing
>     fashion with transactions, but it can be more efficient to batch
>     multiple updates even when some of them are allowed to fail in a
>     best-effort manner.  A new "best effort batches of updates" mode
> @@ -53,7 +53,7 @@ UI, Workflows & Features
>  
>   * The build procedure installs bash (but not zsh) completion script.
>  
> - * send-email has been updated to work better with Outlook's smtp server.
> + * send-email has been updated to work better with Outlook's SMTP server.
>  
>   * "git diff --minimal" used to give non-minimal output when its
>     optimization kicked in, which has been disabled.
> @@ -62,7 +62,7 @@ UI, Workflows & Features
>     delta chains from forming in a corner case even when there is no
>     such cycle.
>  
> - * Make repository clean-up tasks "gc" can do available to "git
> + * Make repository clean-up tasks that "gc" can do available to "git
>     maintenance" front-end.
>  
>   * Bundle-URI feature did not use refs recorded in the bundle other
> @@ -188,7 +188,7 @@ Performance, Internal Implementation, Development Support etc.
>     been dropped.
>  
>   * The code path to access the "packed-refs" file while "fsck" is
> -   taught to mmap the file, instead of reading the whole file in the
> +   taught to mmap the file, instead of reading the whole file into
>     memory.
>  
>   * Assorted fixes for issues found with CodeQL.
> @@ -391,14 +391,13 @@ Fixes since v2.49
>     reverse failed to give the mode bits of the path "removed" by the
>     patch to the file it creates, which has been corrected.
>  
> - * "git verify-refs" (and hence "git fsck --reference") started
> -   erroring out in a repository in which secondary worktrees were
> -   prepared with Git 2.43 or lower.
> + * "git verify-refs" errored out in a repository in which
> +   linked worktrees were prepared with Git 2.43 or lower.
>     (merge d5b3c38b8a sj/ref-contents-check-fix later to maint).
>  
> - * Update total_ram() functrion on BSD variants.
> + * Update total_ram() function on BSD variants.
>  
> - * Update online_cpus() functrion on BSD variants.
> + * Update online_cpus() function on BSD variants.
>  
>   * Other code cleanup, docfix, build fix, etc.
>     (merge 227c4f33a0 ja/doc-block-delimiter-markup-fix later to maint).
>
> base-commit: 4c0e625c091d4c648cec7319bafaed3cc81658e5

      reply	other threads:[~2025-06-11 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 17:35 [PATCH] RelNotes/2.50.0: fix typos & other improvements kristofferhaugsbakk
2025-06-11 19:34 ` 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=xmqq34c6hy36.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=code@khaugsbakk$(echo .)name \
    --cc=git@vger$(echo .)kernel.org \
    --cc=kristofferhaugsbakk@fastmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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