Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: "Dennis Lambe Jr." <malsyned@malsyned.net>,  gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH 0/5] [PR gdb/33469] mi, python: Fix comma location when unwinder emits async records
Date: Thu, 19 Feb 2026 11:27:28 -0700	[thread overview]
Message-ID: <871pig612n.fsf@tromey.com> (raw)
In-Reply-To: <878qhqefq7.fsf@tromey.com> (Tom Tromey's message of "Sat, 04 Oct 2025 11:31:12 -0600")

>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:

>>>>> "Dennis" == Dennis Lambe <malsyned@malsyned.net> writes:
Dennis> I filled out the copyright assignment paperwork in 2018 to contribute
Dennis> to diffutils, does that carry over to binutils as well or do I need to
Dennis> sign separate paperwork for that?

Tom> Unfortunately you do need separate paperwork for gdb.

Hi, did this ever get sorted out?

thanks,
Tom

  reply	other threads:[~2026-02-19 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 23:18 Dennis Lambe Jr.
2025-09-22 23:18 ` [RFC][PATCH 1/5] [PR gdb/33469] ui_out: add optional async param to redirect() Dennis Lambe Jr.
2025-09-22 23:18 ` [RFC][PATCH 2/5] [PR gdb/33469] ui_out_redirect_pop: add optional async param Dennis Lambe Jr.
2025-09-22 23:18 ` [RFC][PATCH 3/5] [PR gdb/33469] mi_ui_out: redirect: push separator state when async = true Dennis Lambe Jr.
2025-09-22 23:18 ` [RFC][PATCH 4/5] [PR gdb/33469] mi-interp: on_param_changed: pass async = true to redirect() Dennis Lambe Jr.
2025-09-22 23:18 ` [RFC][PATCH 5/5] [PR gdb/33469] testsuite: framefilters-mi: async records from unwinder Dennis Lambe Jr.
2025-10-03 18:39 ` [RFC][PATCH 0/5] [PR gdb/33469] mi, python: Fix comma location when unwinder emits async records Tom Tromey
2025-10-03 21:43   ` Dennis Lambe Jr.
2025-10-04 17:31     ` Tom Tromey
2026-02-19 18:27       ` Tom Tromey [this message]
2026-02-19 18:58         ` Dennis Lambe Jr.

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=871pig612n.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=malsyned@malsyned.net \
    /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