public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/110651] libgfortran.spec links twice with libgcc spec Date: Sun, 11 Feb 2024 13:53:12 +0000 [thread overview] Message-ID: <bug-110651-4-nsINMzuEC3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110651-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110651 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- Didn't have any fallout reported, so let's go. Backported to 13 as https://gcc.gnu.org/git?p=gcc.git;a=commit;h=0ea5efea8f24e182b17c7f4f2e3923a2938a2de3 Backported to 12 as https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=56071adae867e63248816f5879339eec27785383 Backported to 11 as https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=407100bffa8c66e92fd4f6bfd2a083995b9dab93
prev parent reply other threads:[~2024-02-11 13:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-13 9:22 [Bug libfortran/110651] New: " ro at gcc dot gnu.org 2023-07-13 9:22 ` [Bug libfortran/110651] " ro at gcc dot gnu.org 2023-07-13 9:30 ` iains at gcc dot gnu.org 2023-07-13 9:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-07-21 11:39 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-12-19 8:17 ` fxcoudert at gcc dot gnu.org 2024-02-10 15:48 ` iains at gcc dot gnu.org 2024-02-11 13:53 ` fxcoudert at gcc dot gnu.org [this message]
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-110651-4-nsINMzuEC3@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).