From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>,
Simon Marchi <simon.marchi@efficios.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] gdbserver: rename source files to .cc
Date: Thu, 13 Feb 2020 15:28:00 -0000 [thread overview]
Message-ID: <BYAPR11MB3030FC28907269502751F7B5C41A0@BYAPR11MB3030.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3229849b-45f7-0863-ba4b-8d650e8b515f@simark.ca>
On Thursday, February 13, 2020 3:49 PM, Simon Marchi wrote:
> On 2020-02-13 9:05 a.m., Tom Tromey wrote:
> >>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
> >
> > Simon> For the same reasons outlined in the previous patch, this patch renames
> > Simon> gdbserver source files to .cc.
> >
> > I support this as well, but I wonder if it would be easier for Tankut if
> > we held off landing this patch until his big target_ops series goes in.
> >
> > Tom
> >
>
> I just tried applying his series over mine with `git am -3` (using git 2.25, if
> that matters), and it applied just fine. Otherwise, supposing I merge mine, using
> git-rebase to rebase his branch on master should work fine as well.
>
> Simon
Thanks for checking this!
-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
next prev parent reply other threads:[~2020-02-13 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 22:54 [PATCH 1/2] gdbsupport: " Simon Marchi
2020-02-12 22:54 ` [PATCH 2/2] gdbserver: " Simon Marchi
2020-02-13 14:05 ` Tom Tromey
2020-02-13 14:48 ` Simon Marchi
2020-02-13 15:08 ` Tom Tromey
2020-02-13 15:28 ` Aktemur, Tankut Baris [this message]
2020-02-13 14:05 ` [PATCH 1/2] gdbsupport: " Tom Tromey
2020-02-13 14:41 ` Simon Marchi
2020-02-13 18:34 ` Pedro Alves
2020-02-13 21:22 ` Simon Marchi
2020-02-13 21:26 ` Pedro Alves
2020-02-13 21:31 ` Simon Marchi
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=BYAPR11MB3030FC28907269502751F7B5C41A0@BYAPR11MB3030.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.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