public inbox for
 help / color / mirror / Atom feed
From: Andreas Schwab <>
To: Jan Beulich via Binutils <>
Cc: Mark Wielaard <>,  Jan Beulich <>,,,
	 Thomas Fitzsimmons <>,
Subject: Re: buildbot users try branch builders
Date: Wed, 22 Jun 2022 09:30:22 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Jan Beulich via Binutils's message of "Wed, 22 Jun 2022 08:32:34 +0200")

On Jun 22 2022, Jan Beulich via Binutils wrote:

> release branches. Hence in .git/config
> 	fetch = +refs/heads/*:refs/remotes/origin/*
> is too wide while limiting to just master is too narrow.

With the latest git version, you can have negative refspecs.

           If a refspec is prefixed by ^, it will be interpreted as a negative
           refspec. Rather than specifying which refs to fetch or which local
           refs to update, such a refspec will instead specify refs to
           exclude. A ref will be considered to match if it matches at least
           one positive refspec, and does not match any negative refspec.
           Negative refspecs can be useful to restrict the scope of a pattern
           refspec so that it will not include specific refs. Negative
           refspecs can themselves be pattern refspecs. However, they may only
           contain a <src> and do not specify a <dst>. Fully spelled out hex
           object names are also not supported.

Andreas Schwab, SUSE Labs,
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2022-06-22  7:30 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 [this message]
2022-06-22 10:51   ` Mark Wielaard
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).