Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Fabian Kilger <kilger@sec.in.tum.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2][PR GDB/32956] gdb: query inferior's filesystem for build-id debug files
Date: Wed, 11 Jun 2025 10:35:04 +0100	[thread overview]
Message-ID: <875xh2iptj.fsf@redhat.com> (raw)
In-Reply-To: <85608652-8d05-436b-b099-9ea72247079d@sec.in.tum.de>

Fabian Kilger <kilger@sec.in.tum.de> writes:

> No problem, thanks for getting back to me. As a first-time contributor
> I'm a bit confused about the rules regarding merging and pushing.
> According to gdb/MAINTAINERS, I should not have write access and need to
> be first added, correct? And according to
>   https://sourceware.org/gdb/wiki/ContributionChecklist
> a moderator or maintainer needs to send me a form regarding FSF
> copyright assignment first.
>
> I would appreciate some clarifications/instructions on what to do
> next.

Unless those forms are stored somewhere that I'm not aware of, then I
don't believe I have access to them, hopefully a maintainer that does
can share them with you.

Failing that, this page:

  https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html

suggests you could just email assign@gnu.org explain what projects you
wish to contribute too, and they will send you back the required
(e-)papers to fill in.

Before then, I could push this second patch for you, if you're happy for
me to do that.

>
> I've also prepared a PATCH v2 for the remaining changes, but wasn't sure
> about some style points I asked about in:
>
>
> https://inbox.sourceware.org/gdb-patches/06881879-1236-4ad7-b983-c195c1c0a84a@sec.in.tum.de/

I'll take a read through, and follow up there.

Thanks,
Andrew


  reply	other threads:[~2025-06-11  9:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11 15:01 [PATCH 0/2][PR GDB/32956] gdb: fix GDB failing to find build-id debug files in linux mount namespaces Fabian Kilger
2025-05-11 15:01 ` [PATCH 1/2][PR GDB/32956] gdb: implement linux namespace support for fileio_stat Fabian Kilger
2025-05-23 18:14   ` Andrew Burgess
2025-05-24 20:25     ` Fabian Kilger
2025-06-11  9:43       ` Andrew Burgess
2025-05-24 10:46   ` Andrew Burgess
2025-05-24 19:43     ` Fabian Kilger
2025-05-24 20:43       ` Fabian Kilger
2025-06-11  9:47         ` Andrew Burgess
2025-06-11  9:58           ` Andrew Burgess
2025-06-11 13:29             ` Tom Tromey
2025-06-11 14:47               ` Andrew Burgess
2025-06-11 17:45                 ` Tom Tromey
2025-06-11 15:06             ` Fabian Kilger
2025-05-11 15:01 ` [PATCH 2/2][PR GDB/32956] gdb: query inferior's filesystem for build-id debug files Fabian Kilger
2025-05-23 18:20   ` Andrew Burgess
2025-05-24 19:54     ` Fabian Kilger
2025-06-10  9:10       ` Andrew Burgess
2025-06-11  8:11         ` Fabian Kilger
2025-06-11  9:35           ` Andrew Burgess [this message]
2025-06-11 14:00             ` Simon Marchi
2025-05-30 19:50 ` [PATCH 0/2][PR GDB/32956] gdb: fix GDB failing to find build-id debug files in linux mount namespaces Tom Tromey
2025-06-10 17:02   ` Andrew Burgess

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=875xh2iptj.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kilger@sec.in.tum.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