public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Merge #1681 Date: Fri, 9 Dec 2022 11:40:59 +0000 (GMT) [thread overview] Message-ID: <20221209114100.25E073833E91@sourceware.org> (raw) https://gcc.gnu.org/g:e91b6e5339c36ecd4b6fc103c39d38757b1c7e4a commit e91b6e5339c36ecd4b6fc103c39d38757b1c7e4a Merge: d0cb3248ce6 d77d5be0695 Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Fri Dec 9 09:31:27 2022 +0000 Merge #1681 1681: Backport #1653 r=CohenArthur a=CohenArthur Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com> Diff: gcc/rust/rust-gcc.cc | 1 + 1 file changed, 1 insertion(+)
reply other threads:[~2022-12-09 11:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221209114100.25E073833E91@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).