From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Minor NEWS rearrangement
Date: Fri, 14 Jun 2019 19:01:00 -0000 [thread overview]
Message-ID: <83v9x8vvmu.fsf@gnu.org> (raw)
In-Reply-To: <20190614183130.8216-1-tromey@adacore.com> (message from Tom Tromey on Fri, 14 Jun 2019 12:31:30 -0600)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Fri, 14 Jun 2019 12:31:30 -0600
>
> I noticed that a NEWS item about Python scripting changes appeared
> between an item about a convenience function and an item about a
> convenience variable. I think it's better for the latter to be next
> to each other.
Fine with me, thanks.
prev parent reply other threads:[~2019-06-14 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 18:31 Tom Tromey
2019-06-14 19:01 ` 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=83v9x8vvmu.fsf@gnu.org \
--to=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