public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "palmer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109668] 'python' vs. 'python3' Date: Fri, 09 Feb 2024 16:55:06 +0000 [thread overview] Message-ID: <bug-109668-4-wjTVGjA20w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109668-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109668 palmer at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palmer at gcc dot gnu.org --- Comment #3 from palmer at gcc dot gnu.org --- Jan-Benedict Glaw is reporting (via a crosstool-ng bug <https://github.com/crosstool-ng/crosstool-ng/issues/2039>) that we've got a few python2 scripts in the RISC-V port that can just be converted over. I just sent along a patch to clean that up.
next prev parent reply other threads:[~2024-02-09 16:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 12:35 [Bug other/109668] New: " tschwinge at gcc dot gnu.org 2023-05-09 11:41 ` [Bug other/109668] " marxin at gcc dot gnu.org 2023-10-24 7:46 ` piannetta at kalrayinc dot com 2024-02-09 16:55 ` palmer at gcc dot gnu.org [this message] 2024-02-23 4:36 ` cvs-commit at gcc dot gnu.org 2024-03-08 14:27 ` cvs-commit at gcc dot gnu.org 2024-03-15 23:29 ` cvs-commit 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-109668-4-wjTVGjA20w@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).