public inbox for
 help / color / mirror / Atom feed
From: Jan Beulich <>
To: Andreas Schwab <>
	Thomas Fitzsimmons <>,,,
	Mark Wielaard <>
Subject: Re: buildbot users try branch builders
Date: Mon, 4 Jul 2022 08:39:04 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 22.06.2022 13:04, Andreas Schwab wrote:
> On Jun 22 2022, Mark Wielaard wrote:
>> 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)
> The user branches are under a different name space (refs/users).  Only
> refs/heads/devel is matched in addition to the release and master
> branches.

I don't speak enough git to be able to tell in how far it is related,
but looking at just the output of a pull done a minute ago I see that
it also fetched

   bf5ddcecc07c..f0a8e7c6fed0  users/ARM/morello-binutils-gdb-master -> origin/users/ARM/morello-binutils-gdb-master

Perhaps I misread your reply by interpreting it to mean Mark's
suggestion won't make a difference, and hence a negative fetch line
like suggested by is pointless to add (for being default behavior
anyway)? (I didn't add or alter any of the fetch lines yet, I'm
merely still in the process of figuring what exactly I need to
change such that it would have the intended effect of not fetching
anything that's under users/.)


  reply	other threads:[~2022-07-04  6:39 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
2022-06-22 11:04     ` Andreas Schwab
2022-07-04  6:39       ` Jan Beulich [this message]
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).