From: Simon Marchi <simark@simark.ca>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, obvious] Fix whitespace in gdb.base/skip.exp
Date: Tue, 17 Dec 2019 16:04:00 -0000 [thread overview]
Message-ID: <a7db167f-128b-b52d-cfba-8aee29105526@simark.ca> (raw)
In-Reply-To: <AM0PR08MB37146AA163DDF4BBD6AB821EE4500@AM0PR08MB3714.eurprd08.prod.outlook.com>
On 2019-12-17 9:56 a.m., Bernd Edlinger wrote:
> Hi,
>
> this fixes just the whitespace issue in gdb.base/skip.exp.
>
> Is it OK for trunk?
>
>
> Thanks
> Bernd.
>
Thanks, I pushed it.
Btw, the preferred way of sending a patch on a mailing list is by using
git-send-email. It sends the email with the patch as the body, making
it easier to comment on it. Could you try to use that for the next patches?
Simon
prev parent reply other threads:[~2019-12-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:56 Bernd Edlinger
2019-12-17 16:04 ` 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=a7db167f-128b-b52d-cfba-8aee29105526@simark.ca \
--to=simark@simark.ca \
--cc=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
/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