From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: RFA: patch NEWS for MI changes (Was: [0/3] RFC: fix PR mi/8444)
Date: Tue, 06 Dec 2011 05:47:00 -0000 [thread overview]
Message-ID: <837h2abbu6.fsf@gnu.org> (raw)
In-Reply-To: <m3wraaofg1.fsf_-_@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 05 Dec 2011 14:51:10 -0700
>
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> Pedro> I think this should have a NEWS entry. MI changes should
> Pedro> be advertised so frontend maintainers notice them.
>
> I agree.
>
> I went through ChangeLog and looked at the various MI changes from this
> year. This is what I came up with.
>
> Ok?
Yes, thanks.
prev parent reply other threads:[~2011-12-06 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 19:58 [0/3] RFC: fix PR mi/8444 Tom Tromey
2011-12-04 14:59 ` Pedro Alves
2011-12-05 21:52 ` RFA: patch NEWS for MI changes (Was: [0/3] RFC: fix PR mi/8444) Tom Tromey
2011-12-06 5:47 ` Eli Zaretskii [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=837h2abbu6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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