From: Petr Tesarik <ptesarik@suse.cz>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org,
Simon Marchi <simon.marchi@polymtl.ca>,
John Baldwin <jhb@freebsd.org>, Jeff Mahoney <jeffm@suse.com>
Subject: Re: [PATCH 0/4] Allow loading symbol files with an offset
Date: Mon, 11 Jun 2018 09:41:00 -0000 [thread overview]
Message-ID: <20180611114143.734171fd@ezekiel.suse.cz> (raw)
In-Reply-To: <95cb3937-99e8-297c-a026-5ab3b86fc154@redhat.com>
On Fri, 8 Jun 2018 14:34:13 +0100
Pedro Alves <palves@redhat.com> wrote:
> On 06/08/2018 01:39 PM, Petr Tesarik wrote:
> > From: Petr Tesarik <petr@tesarici.cz>
> >
> > Implement an "-o" option for symbol-file and add-symbol-file.
>
> Seems like this is missing gdb/NEWS entries for both the new
> -o options, and for making the address argument of add-symbol-file
> optional.
Oh, I did not think about the NEWS file.
> Note that the de facto standard in gdb is for each commit to
> have its own separate ChangeLog entry with date/author header instead
> of appending to the previous entry.
That's what Emacs' add-change-log-entry did by default. I'll go find
out I can force it to start a new entry if the same author makes another
change on the same day...
Anyway, thank you for all the feedback!
Petr T
next prev parent reply other threads:[~2018-06-11 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 12:40 Petr Tesarik
2018-06-08 12:40 ` [PATCH 3/4] Make sure that sorting does not change section order Petr Tesarik
2018-06-08 12:40 ` [PATCH 1/4] Add an optional offset option to the "symbol-file" command Petr Tesarik
2018-06-08 12:59 ` Tom Tromey
2018-06-08 13:09 ` Eli Zaretskii
2018-06-08 12:40 ` [PATCH 4/4] Add an optional offset option to the "add-symbol-file" command Petr Tesarik
2018-06-08 12:53 ` [PATCH 2/4] Make add-symbol-file's address argument optional Petr Tesarik
2018-06-08 13:11 ` Eli Zaretskii
2018-06-08 13:34 ` [PATCH 0/4] Allow loading symbol files with an offset Pedro Alves
2018-06-11 9:41 ` Petr Tesarik [this message]
2018-06-11 18:41 ` Petr Tesarik
2018-06-11 19:10 ` Eli Zaretskii
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=20180611114143.734171fd@ezekiel.suse.cz \
--to=ptesarik@suse.cz \
--cc=gdb-patches@sourceware.org \
--cc=jeffm@suse.com \
--cc=jhb@freebsd.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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).