From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [BUG] Git 2.28.0-rc1 t1800 message text comparison
Date: Thu, 22 Sep 2022 15:01:40 -0400 [thread overview]
Message-ID: <022e01d8ceb5$c2da52c0$488ef840$@nexbridge.com> (raw)
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.
Regards,
Randall
next reply other threads:[~2022-09-22 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:01 rsbecker [this message]
2022-09-22 19:02 ` [BUG] Git 2.38.0-rc1 t1800 message text comparison rsbecker
2022-09-23 20:43 ` rsbecker
2022-12-14 5:53 ` rsbecker
2023-05-22 20:39 ` René Scharfe
2023-05-22 20:49 ` rsbecker
2023-05-22 21:13 ` rsbecker
2023-06-04 12:13 ` René Scharfe
2023-06-04 20:55 ` René Scharfe
2023-06-06 0:31 ` Junio C Hamano
2023-06-10 14:51 ` [PATCH 1/2] t1800: loosen matching of error message for bad shebang René Scharfe
2023-06-12 18:01 ` Junio C Hamano
2023-06-10 14:51 ` [PATCH 2/2] run-command: report exec error even on ENOENT René Scharfe
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='022e01d8ceb5$c2da52c0$488ef840$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--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.