From: Mark Wielaard <mark@klomp.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
gcc-rust@gcc.gnu.org
Subject: Re: Merge from GCC upstream into GCC/Rust
Date: Sat, 25 Sep 2021 13:31:47 +0200 [thread overview]
Message-ID: <YU8Io3hE6vZiGKXV@wildebeest.org> (raw)
In-Reply-To: <87czoyz888.fsf@euler.schwinge.homeip.net>
Hi Thomas,
On Fri, Sep 24, 2021 at 10:30:15AM +0200, Thomas Schwinge wrote:
> I'm preparing a merge from GCC upstream into GCC/Rust. This is normally
> pretty unexciting ;-) -- the exception being, as once mentioned in
> <https://github.com/Rust-GCC/gccrs/issues/247#issuecomment-812720604>:
Thanks for doing this.
> As for checking that the configurations that you're testing are still
> fine, would you like to do (and/or fix) that before or after me pushing
> the merge?
I don't run the builds by hand, the buildbot workers (debian-arm64,
debian-i386, fedora-ppc64, fedora-ppc64le, fedora-s390x,
fedora-x86_64) simply build every new commit they see:
https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust
They are currently all green. If any turns red, they should sent an
email to the list and I'll take a look and try to fix them up.
Cheers,
Mark
next prev parent reply other threads:[~2021-09-25 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 8:30 Thomas Schwinge
2021-09-24 9:25 ` John Paul Adrian Glaubitz
2021-09-24 11:20 ` Philip Herron
2021-09-24 11:45 ` John Paul Adrian Glaubitz
2021-09-25 11:31 ` Mark Wielaard [this message]
2021-09-25 11:52 ` Thomas Schwinge
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=YU8Io3hE6vZiGKXV@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=thomas@codesourcery.com \
/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).