public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109602] Import Gentoo msgfmt patch ?
Date: Mon, 24 Apr 2023 12:37:33 +0000 [thread overview]
Message-ID: <bug-109602-4-P9Qib5mkWv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109602-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sjames at gcc dot gnu.org
--- Comment #4 from Sam James <sjames at gcc dot gnu.org> ---
Arsen is, of course, spot on, but to add some more notes:
- Please in future, don't unilaterally send downstream patches upstream without
attempting to speak to us first. This is on our list to send upstream and
hasn't been yet for the reasons Arsen describes (it needs tidying + proper
rationale included). We're very easily reached and this caught me *very* off
guard.
- The issues for gettext come from msgfmt->libxml2->icu, but it also happens
(we have a similar patch) for when using libarchive tar instead of GNU tar too.
next prev parent reply other threads:[~2023-04-24 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 0:09 [Bug libstdc++/109602] New: " romain.geissler at amadeus dot com
2023-04-24 0:12 ` [Bug libstdc++/109602] " pinskia at gcc dot gnu.org
2023-04-24 0:14 ` pinskia at gcc dot gnu.org
2023-04-24 8:16 ` arsen at gcc dot gnu.org
2023-04-24 12:37 ` sjames at gcc dot gnu.org [this message]
2023-04-24 12:42 ` romain.geissler at amadeus dot com
2023-04-24 19:46 ` arsen 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-109602-4-P9Qib5mkWv@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: link
Be 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).