public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Tom de Vries <tdevries@suse.de>
Cc: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.arch/i386-signal.exp on x86_64
Date: Mon, 16 Oct 2023 09:53:26 +0200	[thread overview]
Message-ID: <1141f1a0-0910-3194-6247-20a50b898d05@suse.com> (raw)
In-Reply-To: <5960f945-4677-49a8-8a51-38e0e0d4fd6c@suse.de>

On 07.10.2023 10:37, Tom de Vries wrote:
> I've committed after adding a note about 
> https://sourceware.org/pipermail/binutils/2023-October/129818.html to 
> the commit log.

Perhaps the better course of action would have been to backport
fb1c10585ead to the respective gdb branch(es)?

Jan

  reply	other threads:[~2023-10-16  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 11:14 Tom de Vries
2023-10-06 22:06 ` John Baldwin
2023-10-07  8:37   ` Tom de Vries
2023-10-16  7:53     ` Jan Beulich [this message]
2023-10-16  8:23       ` Tom de Vries

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=1141f1a0-0910-3194-6247-20a50b898d05@suse.com \
    --to=jbeulich@suse.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=tdevries@suse.de \
    /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).