From: "J.P." <jp@neverwas.me>
To: 53889@debbugs.gnu.org
Subject: bug#53889: 29.0.50; obsolete git-sh-setup function sane_egrep in pre-commit hook
Date: Thu, 24 Feb 2022 22:56:42 -0800 [thread overview]
Message-ID: <87lexzmo2d.fsf@neverwas.me> (raw)
In-Reply-To: <87h798bttg.fsf@neverwas.me> (J. P.'s message of "Tue, 08 Feb 2022 19:30:19 -0800")
This was fixed by:
commit b8a96f055624f86fe965a0d1b7b2495b2db80e63
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Wed Feb 23 11:29:56 2022 -0800
Port pre-commit hook to Git 2.35.0
* build-aux/git-hooks/pre-commit: Use LC_ALL=C grep -E instead of
sane_egrep (removed in Git 2.35.0).
bug#32452: 26.1; gnutls_try_handshake maxes out cpu retrying when server is a bit busy
https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-02/msg01798.html
prev parent reply other threads:[~2022-02-25 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 3:30 bug#53889: 29.0.50; obsolete git-sh-setup function sane_egrep in pre-commit hook J.P.
2022-02-25 6:56 ` J.P. [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lexzmo2d.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=53889@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).