From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Fix scm-ports.exp regression
Date: Mon, 15 Jan 2018 20:59:00 -0000 [thread overview]
Message-ID: <87a7xe6dop.fsf@redhat.com> (raw)
In-Reply-To: <87po6bugv1.fsf@tromey.com> (Tom Tromey's message of "Mon, 15 Jan 2018 11:17:06 -0700")
On Monday, January 15 2018, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> The patch is fine with me as is. I just wish the commit
> Pedro> log were a little clearer with details such as the above.
>
> I added my explanation to the commit message.
> I'm going to push this to the 8.0 branch and trunk.
Hey Tom,
Perhaps you meant to push this to the 8.1 branch?
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-01-15 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 18:20 Tom Tromey
2018-01-05 17:01 ` Pedro Alves
2018-01-09 18:27 ` Tom Tromey
2018-01-15 16:51 ` Pedro Alves
2018-01-15 18:17 ` Tom Tromey
2018-01-15 20:59 ` Sergio Durigan Junior [this message]
2018-01-15 22:10 ` Tom Tromey
2018-01-16 7:39 ` Joel Brobecker
2018-01-05 17:59 Doug Evans via gdb-patches
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=87a7xe6dop.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).