From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17672 invoked by alias); 22 Aug 2017 20:08:40 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 17641 invoked by uid 89); 22 Aug 2017 20:08:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:582 X-Spam-User: qpsmtpd, 2 recipients X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 Aug 2017 20:08:37 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=svr-ies-mbx-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1dkFTW-0005lE-Pe from joseph_myers@mentor.com ; Tue, 22 Aug 2017 13:08:34 -0700 Received: from digraph.polyomino.org.uk (137.202.0.87) by svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 22 Aug 2017 21:08:32 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1dkFTQ-0004Ml-EG; Tue, 22 Aug 2017 20:08:28 +0000 Date: Tue, 22 Aug 2017 20:08:00 -0000 From: Joseph Myers To: Pedro Alves CC: "binutils@sourceware.org" , "gdb@sourceware.org" , Joel Brobecker Subject: Re: can't push to binutils-gdb, git-hooks rejecting commits In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-08/txt/msg00059.txt.bz2 One file corrupted in the disk corruption was the packed-refs file for binutils-gdb. It was restored from backup, but it's possible the resulting refs might either have conflicted with unpacked refs in the refs directory (perhaps someone should check for such conflicts), or have been out of date compared to the tips of those branches at the time of the disk corruption. I don't know if that's how refs got into a problem state rejecting pushes, but it's at least plausible. -- Joseph S. Myers joseph@codesourcery.com