From: "Aktemur, Tankut Baris via Gdb-patches" <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb/breakpoint: make a copy of the "commands" command's argument
Date: Fri, 25 Sep 2020 16:13:43 +0000 [thread overview]
Message-ID: <SN6PR11MB289354F6D4126F75A41F9268C4360@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87tuvmnhqe.fsf@tromey.com>
On Friday, September 25, 2020 2:50 PM, Tom Tromey wrote:
> >> > I forgot to mention -- this seems like a good candidate to apply to the
> >> > gdb 10 branch as well.
>
> >> What is the policy for a release branch? Should I simply cherry-pick the patch from
> >> master and apply to the gdb-10 branch?
>
> >> Shall I apply the patch to the gdb-10-branch, too?
>
> Oops, I'm sorry I didn't respond.
> You can cherry-pick the patch. I suppose you should probably update the
> ChangeLog date.
>
> Tom
Pushed with the updated date. Thanks.
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2020-09-25 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 9:25 Tankut Baris Aktemur
2020-09-16 13:42 ` Tom Tromey
2020-09-16 13:43 ` Tom Tromey
2020-09-16 14:45 ` Aktemur, Tankut Baris
2020-09-25 7:59 ` Aktemur, Tankut Baris via Gdb-patches
2020-09-25 12:50 ` Tom Tromey
2020-09-25 16:13 ` Aktemur, Tankut Baris via Gdb-patches [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=SN6PR11MB289354F6D4126F75A41F9268C4360@SN6PR11MB2893.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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