From: "Schimpe, Christina via Gdb" <gdb@sourceware.org>
To: "Cauble-Chantrenne, Allyson" <Allyson.Cauble-Chantrenne@amd.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Requesting write access to push patch
Date: Fri, 27 Feb 2026 17:02:45 +0000 [thread overview]
Message-ID: <SN7PR11MB76382505B068399E2FF77702F973A@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN7PPF5D27497F1AD3B737C09B8221E2133AA73A@BN7PPF5D27497F1.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Gdb <gdb-bounces~christina.schimpe=intel.com@sourceware.org> On
> Behalf Of Cauble-Chantrenne, Allyson via Gdb
> Sent: Freitag, 27. Februar 2026 16:44
> To: gdb@sourceware.org
> Subject: Requesting write access to push patch
>
> Hello,
>
> I've got a patch for GDB that has been
> approved<https://sourceware.org/pipermail/gdb-patches/2026-
> February/225082.html> and would like to push it. How do I get write access
> to do so?
>
> Thank you,
>
> Allyson
The rule is to have a patch in upstream GDB before you can apply for an account and get write-after-approval access with it. Ask the maintainer that approved your patch about this, they will usually push the first patch for you and approve your status.
See e.g. this thread: https://sourceware.org/pipermail/gdb-patches/2020-September/171791.html
Christina
Intel Deutschland GmbH
Registered Address: Dornacher Straße 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht München HRB 186928
prev parent reply other threads:[~2026-02-27 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:43 Cauble-Chantrenne, Allyson via Gdb
2026-02-27 17:02 ` Schimpe, Christina via Gdb [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=SN7PR11MB76382505B068399E2FF77702F973A@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=gdb@sourceware.org \
--cc=Allyson.Cauble-Chantrenne@amd.com \
--cc=christina.schimpe@intel.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