git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/RelNotes: fix a typo in 2.36's relnotes
Date: Wed, 13 Apr 2022 14:13:31 -0700	[thread overview]
Message-ID: <xmqqczhk7klg.fsf@gitster.g> (raw)
In-Reply-To: <d23e51b8dc78651dbd751473c0f8b3dcd6bc3ac6.1649883760.git.me@ttaylorr.com> (Taylor Blau's message of "Wed, 13 Apr 2022 17:03:28 -0400")

Taylor Blau <me@ttaylorr.com> writes:

> Signed-off-by: Taylor Blau <me@ttaylorr.com>
> ---
> Noticed while reading the RelNotes for GitHub's release highlights blog
> post.

Thanks as always for highlighting more interesting bits from the
flat-and-bland-list-of-changes which is what I prepare as the
release notes.

> - * A not-so-common mistake is to write a script to feed "git bisect
> + * A not-so-uncommon mistake is to write a script to feed "git bisect
>     run" without making it executable, in which case all tests will

I actually meant that this is "not a common mistake that deserves our
bandwidth but because a change was already made to help such a case,
why not take it".

We can probably rewrite _without_ mentioning our expectation of how
common it would be.

    A user can forget to make a script file executable before giving
    it to "git bisect run".  In such a case, all tests will exit ...

  reply	other threads:[~2022-04-13 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 21:03 [PATCH] Documentation/RelNotes: fix a typo in 2.36's relnotes Taylor Blau
2022-04-13 21:13 ` Junio C Hamano [this message]
2022-04-13 21:46   ` Taylor Blau

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=xmqqczhk7klg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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.
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).