From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <hjl.tools@gmail.com>
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com
 [IPv6:2607:f8b0:4864:20::131])
 by sourceware.org (Postfix) with ESMTPS id 7DF2A385DC02;
 Sat, 11 Apr 2020 15:22:04 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7DF2A385DC02
Received: by mail-il1-x131.google.com with SMTP id d2so4101382ilc.0;
 Sat, 11 Apr 2020 08:22:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=C50T2munhyfUPDheQAajmjU8CXwZM2PD+Y08v0vUDZA=;
 b=b7RULMlwBeen5M7nE5HBc7tdlHl9Za4WK5MkasKxhRYhtXdgo9pTtHWvey+7rhcVeZ
 3w6MIUoBTS8PuLP6U2aqEvtV7U9zcGmmMA4XdTILY9kRp3f5odDCXiscnlGiuJuKuwvN
 ySujONG7GtLEUQGXTo14WZcIkcKmUYYzwiTcyeXBQoR8Dt8iD7rHOCIWu6u6ufXqcea/
 jjiwYnn8u+7giAqPDqj1Ch5LofRj0A4vU6GpApdr6gbZlskn8d4bY44QSLOBWNBueYUm
 QZeX5IfjvpWlU7lviCZyZlfooiNG+gZqgydz2B2bpxa80tHtgNIQHtsI/jaeCxq4zbFg
 17Sg==
X-Gm-Message-State: AGi0PuZswP7V+HW/91cmE5n3E9xuH2TYqEKHB3HU+WIoj2GhGINNz3zt
 L+caknTqQMQEViWxxr+xCyaHVYJGsh2i6Lw/bp0HUr7l
X-Google-Smtp-Source: APiQypLAbUkEwd/MdN9UZBajSbOcfHtA6J80NEFLsqPVSTGKNvoLr2TnKCQILtekGf0o1Rlyj8Am8W2oh2dMKkOFtS0=
X-Received: by 2002:a92:8bc2:: with SMTP id
 i185mr10098415ild.273.1586618524061; 
 Sat, 11 Apr 2020 08:22:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAMe9rOpurK69gUkYyEn80_Qd7p32UxMFRxrAdjZwU479mjK-nw@mail.gmail.com>
 <20200411151337.GD1661286@elastic.org>
In-Reply-To: <20200411151337.GD1661286@elastic.org>
From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Sat, 11 Apr 2020 08:21:28 -0700
Message-ID: <CAMe9rOpQbRSP327Umq-2OPVw6MmfBV==eUVPxuRfF+yMKVLw1g@mail.gmail.com>
Subject: Re: Is git server on sourceware.org in trouble?
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
 Binutils <binutils@sourceware.org>, 
 GDB <gdb@sourceware.org>, GNU C Library <libc-alpha@sourceware.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gdb@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb mailing list <gdb.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/gdb>,
 <mailto:gdb-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/gdb>,
 <mailto:gdb-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2020 15:22:06 -0000

On Sat, Apr 11, 2020 at 8:13 AM Frank Ch. Eigler <fche@elastic.org> wrote:
>
> 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.

I am working on my personal branch in binutils-gdb repo.  Can't binutils-gdb
hooks ignore commits on users/* branches?  Maybe I shouldn't use
binutils-gdb repo for my works on binutils at all.

-- 
H.J.