From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-shells/zsh/files/
Date: Sun, 11 Jun 2023 15:32:16 +0000 (UTC) [thread overview]
Message-ID: <1686497518.c17aa1fdefb5d26ea9f2f318c090298cbba11ab6.sam@gentoo> (raw)
commit: c17aa1fdefb5d26ea9f2f318c090298cbba11ab6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 11 15:31:49 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jun 11 15:31:58 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c17aa1fd
app-shells/zsh: add upstream commit link for egrep fix
Noticed while checking the clang15 patch.
Bug: https://bugs.gentoo.org/869332
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-shells/zsh/files/zsh-5.9-do-not-use-egrep-in-tests.patch | 2 ++
1 file changed, 2 insertions(+)
diff --git a/app-shells/zsh/files/zsh-5.9-do-not-use-egrep-in-tests.patch b/app-shells/zsh/files/zsh-5.9-do-not-use-egrep-in-tests.patch
index 7cf605674e96..070767058c3b 100644
--- a/app-shells/zsh/files/zsh-5.9-do-not-use-egrep-in-tests.patch
+++ b/app-shells/zsh/files/zsh-5.9-do-not-use-egrep-in-tests.patch
@@ -1,3 +1,5 @@
+https://github.com/zsh-users/zsh/commit/4fc5dc0292acd77f17281f451774ba2ca4203026
+
commit 4fc5dc0292acd77f17281f451774ba2ca4203026
Author: Jun-ichi Takimoto <takimoto-j@kba.biglobe.ne.jp>
Date: 2022-09-15 18:56:20 +0900
next reply other threads:[~2023-06-11 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 15:32 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 23:22 [gentoo-commits] repo/gentoo:master commit in: app-shells/zsh/files/ Conrad Kostecki
2024-02-08 17:34 Mike Gilbert
2023-06-11 15:32 Sam James
2022-09-16 1:50 Sam James
2022-05-15 12:45 Lars Wendler
2021-03-21 16:34 Lars Wendler
2019-11-08 2:44 Aaron Bauman
2019-02-14 8:38 Fabian Groffen
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=1686497518.c17aa1fdefb5d26ea9f2f318c090298cbba11ab6.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox