From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: "Martin Liška" <mliska@suse.cz>, "Tom Tromey" <tom@tromey.com>
Cc: Simon Marchi <simark@simark.ca>, "H.J. Lu" <hjl.tools@gmail.com>,
Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: RE: Auto update ChangeLog for binutils+gdb commits?
Date: Sat, 30 May 2020 10:23:25 +0000 [thread overview]
Message-ID: <SN6PR11MB2893D78261A0540095F6E64AC48C0@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <12ea10a1-59c1-5858-4619-ed3b40121d30@suse.cz>
On Friday, May 29, 2020 3:57 PM, Martin Liška wrote:
>
> $ git format-patch -1 2b2558bfacba3813863da6728c021eb89fa34677 && ~/Programming/gcc/contrib/mklog.py 00*
> 0001-Move-DWARF-constant-stringifying-code-to-new-file.patch
>
> ChangeLog:
>
> * gdb/ChangeLog:
> * gdb/Makefile.in:
> * gdb/dwarf2/read.c (dwarf_tag_name):
> (dwarf_attr_name):
> (dwarf_form_name):
> (dwarf_bool_name):
> (dwarf_type_encoding_name):
> (dwarf_unknown):
> * gdb/dwarf2/stringify.c: New file.
> * gdb/dwarf2/stringify.h: New file.
Is this actually correct? I think it should have been
gdb/
* Makefile.in:
* dwarf2/read.c (dwarf_tag_name):
... and so on.
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2020-05-30 10:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:07 Auto generate ChangeLog for binutils commits? H.J. Lu
2020-05-27 14:10 ` Simon Marchi
2020-05-27 14:20 ` H.J. Lu
2020-05-27 14:29 ` Simon Marchi
2020-05-27 15:10 ` Auto update ChangeLog for binutils+gdb commits? H.J. Lu
2020-05-29 7:45 ` Martin Liška
2020-05-29 8:51 ` Martin Liška
2020-05-29 12:15 ` Tom Tromey
2020-05-29 12:25 ` Martin Liška
2020-05-29 12:44 ` Tom Tromey
2020-05-29 13:56 ` Martin Liška
2020-05-30 10:23 ` Aktemur, Tankut Baris [this message]
2020-05-30 11:22 ` Martin Liška
2020-05-30 19:41 ` Tom Tromey
2020-05-31 4:40 ` Fangrui Song
2020-05-31 7:41 ` Jan Vrany
2020-06-01 7:51 ` Martin Liška
2020-05-29 12:28 ` Martin Liška
2020-05-29 13:57 ` Eli Zaretskii
2020-05-30 19:23 ` Tom Tromey
2020-05-30 19:35 ` Eli Zaretskii
2020-06-01 7:39 ` Martin Liška
2020-06-01 14:59 ` Eli Zaretskii
2020-06-02 6:49 ` Martin Liška
2021-01-15 1:18 ` Fangrui Song
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=SN6PR11MB2893D78261A0540095F6E64AC48C0@SN6PR11MB2893.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mliska@suse.cz \
--cc=simark@simark.ca \
--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).