From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: Is git server on sourceware.org in trouble?
Date: Sat, 11 Apr 2020 11:13:37 -0400 [thread overview]
Message-ID: <20200411151337.GD1661286@elastic.org> (raw)
In-Reply-To: <CAMe9rOpurK69gUkYyEn80_Qd7p32UxMFRxrAdjZwU479mjK-nw@mail.gmail.com>
Hi -
> to finish for more than 10 minutes. It looks like one of commit hooks
> never returns.
Some git/hooks/update.* python script in your repo is doing a hideous
number of "git show HASH:every_single_file.c" operations.
- FChE
next prev parent reply other threads:[~2020-04-11 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:07 H.J. Lu
2020-04-11 15:08 ` H.J. Lu
2020-04-11 15:13 ` Frank Ch. Eigler [this message]
2020-04-11 15:21 ` H.J. Lu
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=20200411151337.GD1661286@elastic.org \
--to=fche@elastic.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).