public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rust/108113] Rust and --enable-link-serialization=1 Date: Mon, 19 Dec 2022 08:54:05 +0000 [thread overview] Message-ID: <bug-108113-4-EkSYdP5Muj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108113-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113 --- Comment #3 from Marc Poulhiès <dkm at gcc dot gnu.org> --- I can yes, but wasn't really sure and didn't want to interfere with Arthur ongoing work at updating the gcc's master branch with all the pending changes from github. Should I submit the patch for formal approval on gcc-patches@ or can I go ahead and apply it directly ?
next prev parent reply other threads:[~2022-12-19 8:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 19:49 [Bug rust/108113] New: " jakub at gcc dot gnu.org 2022-12-14 19:59 ` [Bug rust/108113] " dkm at gcc dot gnu.org 2022-12-16 18:35 ` tschwinge at gcc dot gnu.org 2022-12-19 8:54 ` dkm at gcc dot gnu.org [this message] 2022-12-19 11:42 ` tschwinge at gcc dot gnu.org 2022-12-19 11:49 ` jakub at gcc dot gnu.org 2022-12-20 8:12 ` cvs-commit at gcc dot gnu.org 2022-12-20 8:32 ` dkm at gcc dot gnu.org
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=bug-108113-4-EkSYdP5Muj@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).