Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Find debug symbols file by buildid for coff file format also
Date: Tue, 17 Mar 2015 12:56:00 -0000	[thread overview]
Message-ID: <55082466.3010702@dronecode.org.uk> (raw)
In-Reply-To: <831tko29ct.fsf@gnu.org>

On 16/03/2015 16:30, Eli Zaretskii wrote:
[...]
>>
>> gdb/doc/ChangeLog:
>>
>> 2015-03-14  Jon TURNEY  <jon.turney@dronecode.org.uk>
>>
>> 	* gdb.texinfo (Separate Debug Files): Document that COFF is also
>> 	supported.
>
> The gdb.texinfo part is OK, except that AFAIK PE is not the same as
> COFF, so I suggest to amend the ChangeLog entry above.

Yes, this should say PE in the ChangeLog (and subject).



  reply	other threads:[~2015-03-17 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 15:37 Jon TURNEY
2015-03-16 16:30 ` Eli Zaretskii
2015-03-17 12:56   ` Jon TURNEY [this message]
2015-04-08 12:17     ` [PATCH] Find debug symbols file by buildid for PE " Jon TURNEY
2015-04-08 12:39       ` Eli Zaretskii
2015-04-22 13:41       ` Jon TURNEY
2015-06-02 13:33       ` Jon TURNEY
2015-06-09 19:36       ` Joel Brobecker
2015-06-10 14:26         ` [PATCH] Allow gdb to find debug symbols file by build-id " Jon Turney
2015-06-12 15:45           ` Nicholas Clifton
2015-06-15 16:34           ` Mike Frysinger
2015-06-15 18:13             ` Andreas Schwab
2015-06-15 18:25               ` Jon TURNEY
2015-06-16 11:35                 ` Nicholas Clifton
2015-06-17 16:09           ` Yao Qi
2015-06-18 11:05             ` Jon TURNEY

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=55082466.3010702@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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