From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 7EFEA3834F3A; Wed, 22 Jun 2022 10:51:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7EFEA3834F3A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 5F55530006B8; Wed, 22 Jun 2022 12:51:32 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 1D6A04001096; Wed, 22 Jun 2022 12:51:32 +0200 (CEST) Message-ID: Subject: Re: buildbot users try branch builders From: Mark Wielaard To: Jan Beulich Cc: buildbot@sourceware.org, Thomas Fitzsimmons , fche@redhat.com, binutils@sourceware.org, gdb@sourceware.org Date: Wed, 22 Jun 2022 12:51:31 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2022 10:51:34 -0000 Hi Jan, On Wed, 2022-06-22 at 08:32 +0200, Jan Beulich wrote: > I'm not very fluent in git, yet before that might happen I'd like to > figure a way to keep my clone clean of the objects related to such > branches, but without also omitting the objects for, in particular, > release branches. Hence in .git/config >=20 > fetch =3D +refs/heads/*:refs/remotes/origin/* >=20 > is too wide while limiting to just master is too narrow. From earlier > experiments I seem to recall that the *s here can't be simply > replaced by more restricting wildcard "expressions" ... Note that you can have multiple fetch lines, so you can just add a list of explicit refs you want to fetch. But I do see your problem, unlike in gcc where the releases are all under refs/heads/releases/ the binutils and gdb ones are directly under /heads/. Maybe the negative refspecs that Andreas mentioned would help here because all user branches are under /ref/heads/users/ So maybe adding fetch =3D ^refs/heads/users/* would do the trick? (untested) Cheers, Mark