From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 466CD39AFEA4; Mon, 19 Dec 2022 08:54:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 466CD39AFEA4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1671440055; bh=ozJagLvqPw0QlPU6r8U9K3Ll19lFYxoMxMSe1ot+Zew=; h=From:To:Subject:Date:In-Reply-To:References:From; b=x7ByjDeuXaKcM+tj+KUbYSYbcO0citNrbjU7C+2YD+wqjQ/89/tFnOKrukawGWCyC TxjqoLaFZCLlOkDSQ3Vw5TgLTnHBvU0HJxnqm45H5jkSQ4c4iIb/M7W3O7xIZU5+Wy Qzt3k6rbX/Vv6TgYsxuTPeya6yJzk82ZHcELj1v4= From: "dkm at gcc dot gnu.org" To: gcc-rust@gcc.gnu.org Subject: [Bug rust/108113] Rust and --enable-link-serialization=1 Date: Mon, 19 Dec 2022 08:54:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rust X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dkm at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dkm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108113 --- Comment #3 from Marc Poulhi=C3=A8s --- 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 chang= es from github. Should I submit the patch for formal approval on gcc-patches@ or can I go a= head and apply it directly ? --=20 You are receiving this mail because: You are on the CC list for the bug.=