From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: walfred.tedeschi@intel.com, michael.sturm@intel.com,
gdb-patches@sourceware.org, palves@redhat.com,
mark.kettenis@xs4all.nl
Subject: Re: Incorrect placement of two Intel gdb/NEWS items
Date: Mon, 04 Aug 2014 19:17:00 -0000 [thread overview]
Message-ID: <837g2oqd2n.fsf@gnu.org> (raw)
In-Reply-To: <20140804165708.GA12824@host2.jankratochvil.net>
> Date: Mon, 4 Aug 2014 18:57:08 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, palves@redhat.com, mark.kettenis@xs4all.nl
>
> Hi Eli,
>
> there were two commits which placed new gdb/NEWS items to the bottom of the
> NEWS file (such as for gdb-4.0) instead at their right place under:
> *** Changes in GDB 7.8
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=blobdiff;f=gdb/NEWS;h=ae84e009b8008f9da2707829c0cbab358abc17fb;hp=a8ae8c7b7a5ddce9b5779914dd1e6a87463d7d60;hb=ca8941bbd088002cb8ff87abe16d02ecc8d58d1e;hpb=489e41ddf4bb5616a7471fb4072df5efbb9a706e
> commit ca8941bbd088002cb8ff87abe16d02ecc8d58d1e
> Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Date: Tue Dec 3 13:31:03 2013 +0000
> Documentation for MPX.
> Message-Id: <1386074172-14177-1-git-send-email-walfred.tedeschi@intel.com>
> https://sourceware.org/ml/gdb-patches/2013-12/msg00082.html
>
> and
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=blobdiff;f=gdb/NEWS;h=a7067fdf9a7af422572a29d1fdd6ef011c87cd9f;hp=b72d64db313d0785edec19a9c4b441b854698e6a;hb=01f9f808e2e86187c95e7cff4aeb014a421a53ce;hpb=93ee1e3683a12f4774b8beb4f821910982e21ce2
> commit 01f9f808e2e86187c95e7cff4aeb014a421a53ce
> Author: Michael Sturm <michael.sturm@intel.com>
> Date: Mon Dec 16 16:43:05 2013 +0100
> Add AVX512 registers support to GDB and GDBserver.
> Message-Id: <1398258160-9070-4-git-send-email-michael.sturm@intel.com>
> https://sourceware.org/ml/gdb-patches/2013-12/msg00818.html
>
> It would be probably also good to move them in the 7.8 branch for gdb-7.8.1.
Please do. This is a purely technical issue, I'd even say an obvious
fix, so no need to get my approval. (I approve anyway.)
Thanks.
next prev parent reply other threads:[~2014-08-04 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:03 [PATCH V5 0/3] Intel(R) AVX-512 register support Michael Sturm
2014-04-23 13:03 ` [PATCH V5 2/3] Add AVX512 register support to gdbserver Michael Sturm
2014-11-21 10:21 ` Andreas Arnez
2014-12-13 13:41 ` Joel Brobecker
2015-01-08 10:01 ` Sturm, Michael
2015-01-10 7:00 ` Joel Brobecker
2014-04-23 13:03 ` [PATCH V5 3/3] Add AVX512 feature description to GDB manual Michael Sturm
2013-12-03 12:37 ` [PATCH v3 1/1] Documentation for MPX Walfred Tedeschi
2013-12-03 12:52 ` Eli Zaretskii
2014-08-04 16:57 ` Incorrect placement of two Intel gdb/NEWS items Jan Kratochvil
2014-08-04 19:17 ` Eli Zaretskii [this message]
2014-08-04 19:40 ` [commit+7.8] " Jan Kratochvil
2014-04-23 13:04 ` [PATCH V5 1/3] Add AVX512 registers support to GDB Michael Sturm
2014-04-24 11:33 ` Pedro Alves
2014-04-24 11:48 ` Pedro Alves
2014-04-24 11:49 ` [PATCH V5 0/3] Intel(R) AVX-512 register support Pedro Alves
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=837g2oqd2n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=michael.sturm@intel.com \
--cc=palves@redhat.com \
--cc=walfred.tedeschi@intel.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