public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Jan Beulich <>
Cc:, Thomas Fitzsimmons <>,,,
Subject: Re: buildbot users try branch builders
Date: Wed, 22 Jun 2022 12:51:31 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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
> 	fetch = +refs/heads/*:refs/remotes/origin/*
> 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

Maybe the negative refspecs that Andreas mentioned would help here
because all user branches are under /ref/heads/users/ So maybe adding
fetch = ^refs/heads/users/* would do the trick? (untested)



  parent reply	other threads:[~2022-06-22 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 10:48 Mark Wielaard
2022-06-21 10:30 ` Szabolcs Nagy
2022-06-21 17:30   ` Mark Wielaard
2022-06-22  6:32 ` Jan Beulich
2022-06-22  7:30   ` Andreas Schwab
2022-06-22 10:51   ` Mark Wielaard [this message]
2022-06-22 11:04     ` Andreas Schwab
2022-07-04  6:39       ` Jan Beulich
2022-07-04 14:10         ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).