public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, tom@tromey.com, pedro@palves.net
Subject: Re: [PATCH] gdb/NEWS: reorder some entries in the NEWS file
Date: Fri, 06 Oct 2023 13:22:27 +0100	[thread overview]
Message-ID: <871qe8szy4.fsf@redhat.com> (raw)
In-Reply-To: <83v8btx9pq.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
>>  Pedro Alves <pedro@palves.net>
>> Date: Fri, 29 Sep 2023 14:31:19 +0100
>> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>> 
>> 
>> I spotted two entries in the NEWS file that I believe are in the wrong
>> place, these are:
>> 
>>   - An entry about MI v1 being deprecated, this feels like it should
>>     be the first entry under the 'MI changes' heading, and
>> 
>>   - An entry for the $_shell convenience function which is currently
>>     under the 'New commands' heading (sort of), when I think this
>>     should be listed in the general news section.
>> 
>> ---
>> 
>> I've CC'd the authors of the two pieces I've moved in case they
>> object, otherwise I'll push this in a few days.
>
> Thanks, fine by me.

I've gone ahead and pushed this.  If the original authors feel strongly
that their entries shouldn't be moved they can let me know and I'll move
them back.

Thanks,
Andrew


      reply	other threads:[~2023-10-06 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:31 Andrew Burgess
2023-09-29 15:47 ` Eli Zaretskii
2023-10-06 12:22   ` Andrew Burgess [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=871qe8szy4.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).