public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Kévin Le Gouguec" <legouguec@adacore.com>
Cc: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Guard against frame.c destructors running before frame-info.c's
Date: Wed, 16 Nov 2022 11:28:10 -0500	[thread overview]
Message-ID: <e0721db5-a4eb-52f2-dede-cdea4f0c4874@polymtl.ca> (raw)
In-Reply-To: <87sfiiyigy.fsf@adacore.com>

On 11/16/22 11:25, Kévin Le Gouguec wrote:
> Simon Marchi <simon.marchi@polymtl.ca> writes:
> 
>> Do you plan on contributing further and regularly?
> 
> Yep.
> 
>>                                                     If so we'll get you
>> an account on Sourceware.  Otherwise I can push this patch for you.
> 
> Thanks; Joel invited me to fill in the sourceware Account Request Form,
> so I did just now.
> 
> If that's OK, I plan on posting the patch to add myself to
> gdb/MAINTAINERS under "Write After Approval" shortly, and on pushing
> both patches myself when the account is set up.

Perfect, thanks, that's the right process.

Simon

      reply	other threads:[~2022-11-16 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:48 Kévin Le Gouguec
2022-11-15 21:57 ` Simon Marchi
2022-11-15 22:32   ` Kévin Le Gouguec
2022-11-16  1:03   ` Tom Tromey
2022-11-16  1:19     ` Simon Marchi
2022-11-16  7:05       ` Kévin Le Gouguec
2022-11-16 14:39         ` Simon Marchi
2022-11-16 16:25           ` Kévin Le Gouguec
2022-11-16 16:28             ` Simon Marchi [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=e0721db5-a4eb-52f2-dede-cdea4f0c4874@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=legouguec@adacore.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).