list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: <>
To: <>, <>
Subject: RE: [BUG] Git 2.38.0-rc1 t1800 message text comparison
Date: Thu, 22 Sep 2022 15:02:59 -0400	[thread overview]
Message-ID: <023101d8ceb5$f1c28850$d54798f0$> (raw)
In-Reply-To: <022e01d8ceb5$c2da52c0$488ef840$>

On September 22, 2022 3:02 PM, I wrote:
>Rc1 is looking good except for this test.
>We get a diff as follows:
>-fatal: cannot run bad-hooks/test-hook: ...
>+fatal: cannot exec 'bad-hooks/test-hook': Permission denied
>It looks like the pattern
>sed -e s/test-hook: .*/test-hook: .../
>needs to be a bit extended. Adding
>sed -e s/exec/run/ | send -e s/["']//g
>might help clear off the other noise.

The subject should have been 2.38.0, not 2.28.0.

  reply	other threads:[~2022-09-22 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 19:01 [BUG] Git 2.28.0-rc1 t1800 message text comparison rsbecker
2022-09-22 19:02 ` rsbecker [this message]
2022-09-23 20:43 ` [BUG] Git 2.38.0-rc1 " rsbecker

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='023101d8ceb5$f1c28850$d54798f0$' \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).