From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id z4GMC3fCYmCPYAAAWB0awg (envelope-from ) for ; Tue, 30 Mar 2021 02:17:27 -0400 Received: by simark.ca (Postfix, from userid 112) id 20AC21EE0E; Tue, 30 Mar 2021 02:17:27 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 7875A1E783 for ; Tue, 30 Mar 2021 02:17:26 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B0AF13861002; Tue, 30 Mar 2021 06:17:25 +0000 (GMT) Received: from rock.gnat.com (rock.gnat.com [205.232.38.15]) by sourceware.org (Postfix) with ESMTP id 4822938515D6; Tue, 30 Mar 2021 06:17:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4822938515D6 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=adacore.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=brobecker@adacore.com Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 21A8E11706B; Tue, 30 Mar 2021 02:17:23 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at gnat.com 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 AoUVF2xyb8UE; Tue, 30 Mar 2021 02:17:23 -0400 (EDT) Received: from float.home (localhost.localdomain [127.0.0.1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by rock.gnat.com (Postfix) with ESMTPS id BB918117019; Tue, 30 Mar 2021 02:17:22 -0400 (EDT) Received: by float.home (Postfix, from userid 1000) id 93D0FA1242; Tue, 30 Mar 2021 10:17:17 +0400 (+04) Date: Tue, 30 Mar 2021 10:17:17 +0400 From: Joel Brobecker To: Martin =?utf-8?B?TGnFoWth?= , Binutils , gdb-patches@sourceware.org Subject: Re: Please enable fast forward for user branches Message-ID: <20210330061717.GD11111@adacore.com> References: <1af95023-580d-6774-c307-1a38bf3dc073@suse.cz> <20210330040939.GC11111@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" > > I think the error above comes from Git itself, and is related > > to the configuration of the repository. In particular, I found > > that our binutils-gdb repository's configuration has: > > > > | [receive] > > | denynonfastforwards = true > > > > Not sure what the history of this is. > > > > In the meantime, I've modified the git-hooks configuration so that, > > if the above is lifted, users will be allowed to do non-fast-forward > > updates on users/.* branches. > > iiuc, out of the box, the default git implementation has one knob for all > branches (the one you found). we set it that way so people don't push > non-fast-forwards to the important branches (e.g. "master" or any of the > many release branches). that all makes perfect sense -- we don't want > people to accidentally, or on purpose, rewrite (i.e. rewind) history once > it's gone public. > > unfortunately, the default git configs don't have ref filtering to allow > denynonfastforwards=false on refs/heads/users/*. any services that have > that functionality implemented it themselves. which is what we'd have to > do with custom git hooks if we wanted to. but it looks like no one has > volunteered to implement the hook to block most refs by default but only > allow a specific subset. probably because they don't want to be on the > hook for when it needs debugging. Actually, we do use the git-hooks (https://github.com/adacore/git-hooks) which allow per-reference configuration of that restriction. That's what I was trying to explain in my message. Perhaps the receive.denynonfastforwards pre-dates the use of the git-hooks. -- Joel