From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [v2] Fix Rust enum test failures
Date: Wed, 28 Feb 2018 16:12:00 -0000 [thread overview]
Message-ID: <878tbdozys.fsf@tromey.com> (raw)
In-Reply-To: <20180228155503.24537-1-tom@tromey.com> (Tom Tromey's message of "Wed, 28 Feb 2018 08:55:03 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> Pedro pointed out that some Rust tests were failing after the recent
Tom> enum change.
The subject here was supposed to read "[RFA]".
Tom
next prev parent reply other threads:[~2018-02-28 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 15:55 Tom Tromey
2018-02-28 16:12 ` Tom Tromey [this message]
2018-03-01 2:59 ` Joel Brobecker
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=878tbdozys.fsf@tromey.com \
--to=tom@tromey.com \
--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