From: Tom de Vries <tdevries@suse.de>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite, Tcl 9] Fix EILSEQ problems for UTF8 related tests
Date: Thu, 28 May 2026 10:14:54 +0200 [thread overview]
Message-ID: <5ae6b562-a46a-4631-a363-13f34b0b97c8@suse.de> (raw)
In-Reply-To: <20260526124220.487b4e7e@f42-zbm-amd>
On 5/26/26 9:42 PM, Kevin Buettner wrote:
> Hi Tom,
>
> On Tue, 26 May 2026 11:22:19 +0200
> Tom de Vries <tdevries@suse.de> wrote:
>
>> Hi Kevin,
>>
>> this LGTM, so:
>>
>> Reviewed-By: Tom de Vries <tdevries@suse.de>
>>
>> I also reviewed this using Claude code, and there were two notes:
>> - using catch for one fconfigure, but not the other two.
>> - it might be a good idea to add a comment in open_logs to make it
>> explicit that unlike elsewhere, "-profile replace" isn't used.
>
> Thanks for the reviews, both from yourself and from Claude Code.
>
> After discussing it with my own AIs (both Claude and a local Qwen3.6
> 27B), I've made some documentation changes and a minor unrelated code
> tweak, which should address the concerns about the use of "catch" in
> one location, but not the others as well as the reason for the lack of
> "-profile replace". (I didn't want to introduce another form of Tcl
> version guard in open_logs, which is why I investigated whether I
> could dispense with use of "-profile replace".) In any case, I think
> it's now amply documented.
>
> I posted a v2 here:
>
> https://sourceware.org/pipermail/gdb-patches/2026-May/227637.html
>
Hi Kevin,
I've taken a look, no further comments.
Thanks,
- Tom
> Kevin
>
prev parent reply other threads:[~2026-05-28 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 5:14 Kevin Buettner
2026-05-26 9:22 ` Tom de Vries
2026-05-26 19:42 ` Kevin Buettner
2026-05-28 8:14 ` Tom de Vries [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=5ae6b562-a46a-4631-a363-13f34b0b97c8@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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