From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use Solaris iconv
Date: Sat, 22 Aug 2026 22:19:09 +0200 [thread overview]
Message-ID: <yddik51gb7m.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87y0dzse99.fsf@tromey.com> (Tom Tromey's message of "Fri, 21 Aug 2026 09:08:02 -0600")
Hi Tom,
>>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> Rainer> BTW., given the benefit and no impact for other OSes, this might be a
> Rainer> candidate for the GDB 18 release. Thoughts?
>
> Ok for both, thanks a lot.
> Approved-By: Tom Tromey <tom@tromey.com>
I'd already committed the patch to both trunk and gdb-18 branch, sorry.
I'm still a bit confused about the differences in procedure and commit
message contents between gdb, binutils, and gcc.
Thinks like no ChangeLogs in gdb, only in commit message in binutils,
and both in commit message and extracted into actual ChangeLog files in
gcc. Just an ok/lgtm being enough in gcc and binutils vs. git trailers
in gdb... It's harder to wrap your head around this especially if you
only contribute occasionally.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2026-08-22 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:23 Rainer Orth
2026-08-20 16:33 ` Tom Tromey
2026-08-20 18:00 ` Rainer Orth
2026-08-20 18:27 ` Simon Marchi
2026-08-21 15:08 ` Tom Tromey
2026-08-22 20:19 ` Rainer Orth [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=yddik51gb7m.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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