From: Jan Beulich <jbeulich@suse.com>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org, Thomas Fitzsimmons <fitzsim@fitzsim.org>,
fche@redhat.com, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: buildbot users try branch builders
Date: Wed, 22 Jun 2022 08:32:34 +0200 [thread overview]
Message-ID: <f16e1c9a-2ed9-fe2c-30cd-14f2075e69bc@suse.com> (raw)
In-Reply-To: <YrBQZPWg75J0X1UP@wildebeest.org>
On 20.06.2022 12:48, Mark Wielaard wrote:
> As an experiment we now have try builders for binutils and gdb. If you
> have commit access to binutils-gdb.git you can now push to your
> users/<name>/try-xxx branch and the buildbot will do builds and sent
> you (the commit author) email about the results. The builds are also
> visible at:
So I have a (perhaps seemingly unrelated) question here: If this is put
into general use, it'll encourage more people to push to such branches.
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" ...
Jan
next prev parent reply other threads:[~2022-06-22 6:32 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 [this message]
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
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f16e1c9a-2ed9-fe2c-30cd-14f2075e69bc@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=fche@redhat.com \
--cc=fitzsim@fitzsim.org \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).