From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: David Taylor <dtaylor@emc.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix for QTro remote packet
Date: Sat, 11 May 2013 10:38:00 -0000 [thread overview]
Message-ID: <20130511103848.GL9160@adacore.com> (raw)
In-Reply-To: <518D0188.60003@redhat.com>
> As for the 7.6.1 release notes in the wiki, I've went ahead and
> modelled from Joel's entry, and added:
>
> "PR remote/15455 (QTro remote packet broken)"
>
> I think there's no way to get that wrong if Joel's entry is
> good too. :-)
I think that's a good seed, and allows for a concise summary of
the fixes. Anyone interested can get more detailed info from the PR
itself. I have been wondering whether we might want to attach
a more detailed description, but I am afraid that this would
discourage people from reading it. So I think the current approach
is a good balance. Let's evaluate it, and adjust only if we feel
it would be worth it.
--
Joel
prev parent reply other threads:[~2013-05-11 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 17:38 David Taylor
2013-05-02 17:23 ` Pedro Alves
2013-05-10 14:17 ` Pedro Alves
2013-05-11 10:38 ` Joel Brobecker [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=20130511103848.GL9160@adacore.com \
--to=brobecker@adacore.com \
--cc=dtaylor@emc.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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