From: Tom Tromey <tromey@redhat.com>
To: GDB Development <gdb@sourceware.org>
Subject: Re: FYI: fix PR 10684
Date: Wed, 23 Sep 2009 17:49:00 -0000 [thread overview]
Message-ID: <m3tyytmtzx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3y6o5mvd7.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 23 Sep 2009 11:19:48 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I am checking this in on the trunk and the 7.0 branch.
Tom> This patch comes from PR 10684. It is small enough not to require
Tom> paperwork.
Oops, sorry, I sent this to the wrong list.
I meant, of course, to send it to gdb-patches.
Tom
prev parent reply other threads:[~2009-09-23 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 17:19 Tom Tromey
2009-09-23 17: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=m3tyytmtzx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@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