From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle \r\n in gdbreplay
Date: Wed, 27 Feb 2019 18:49:00 -0000 [thread overview]
Message-ID: <8736o95aoq.fsf@tromey.com> (raw)
In-Reply-To: <87y369jfby.fsf@tromey.com> (Tom Tromey's message of "Thu, 21 Feb 2019 09:06:57 -0700")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> commit eb7112d0f11809c25f415fa4f48aa6abe5fd84a4
Tom> Author: Tom Tromey <tromey@adacore.com>
Tom> Date: Wed Feb 20 14:29:23 2019 -0700
Tom> Handle \r\n in gdbreplay
[...]
I'm checking this in now.
Tom
prev parent reply other threads:[~2019-02-27 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 14:05 Tom Tromey
2019-02-21 15:14 ` Eli Zaretskii
2019-02-21 16:07 ` Tom Tromey
2019-02-21 16:12 ` Paul Koning
2019-02-27 18:49 ` Tom Tromey [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=8736o95aoq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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