From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84443 invoked by alias); 22 Aug 2017 15:05:26 -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 83318 invoked by uid 89); 22 Aug 2017 15:05:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=spotty X-Spam-User: qpsmtpd, 2 recipients X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 Aug 2017 15:05:24 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id BFE0D561B6; Tue, 22 Aug 2017 11:05:22 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gZWO72IdaCMo; Tue, 22 Aug 2017 11:05:22 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A3953561B0; Tue, 22 Aug 2017 11:05:22 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id EBCF4809D3; Tue, 22 Aug 2017 11:05:21 -0400 (EDT) Date: Tue, 22 Aug 2017 15:05:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: "binutils@sourceware.org" , "gdb@sourceware.org" Subject: Re: can't push to binutils-gdb, git-hooks rejecting commits Message-ID: <20170822150521.ye7dlqkfcivs5vym@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-08/txt/msg00048.txt.bz2 Hi Pedro, > I'm trying to push a patch to master, but it's getting rejected by the > server-side git hooks. Anyone else seeing the same? See below. > > Repeating that big "git rev-list" command below locally shows: > > fatal: bad revision '^refs/heads/users/hjl/pr17709' > > That branch doesn't appear to exist anymore. Sounds like the hooks > need to run "git remote prune origin" on their clone? Does that make > sense? For me, I get a different error message, but in the same vein: fatal: bad revision '^refs/heads/users/hjl/gpoff' I think it's related to the disk corruption. If the branch stopped existing, git should have removed the associated reference. I would try a "git fsck" to see if it detects any other kinds of issues, and decide how to fix them. For instance, we could delete those branches, and ask HJL to re-push. I don't think the "git remote prune" command was meant for that (I think it'll prune references from refs/remotes/ instead). I can look into this, but as I traveling, availability on my side is a little spotty. -- Joel