This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Make cu/tu functions in dwarf.exp take a list of options
- From: Doug Evans <dje at google dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Mon, 20 May 2013 09:42:34 -0700
- Subject: Re: [RFA] Make cu/tu functions in dwarf.exp take a list of options
- References: <yjt2obc9frdv dot fsf at ruffy dot mtv dot corp dot google dot com> <871u95qy90 dot fsf at fleche dot redhat dot com> <CADPb22QEF-QQGkx_msjF8-3E0OMbfGcB4gBG63POHZzWSAgs0w at mail dot gmail dot com> <20130520054023 dot GL4017 at adacore dot com>
On Sun, May 19, 2013 at 10:40 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> When you change the calling sequence of a function in a simple fashion,
>> and you change all the callers of the function to use the new calling
>> sequence, there is no need to make individual entries for all the
>> callers that you changed. Just write in the entry for the function
>> being called, ``All callers changed''---like this:
>
> FWIW: No real opinion, but I intepreted the above in the context
> of the same file only. I find that listing all the files adjusted
> was fairly easy, so I thought the added information was worth the
> small effort...
"small" can be relative, and we shouldn't IMO be adding effort to
writing ChangeLogs that have incommensurate value.
[For example, we go *way* beyond what is required by standards.texi
for doc ChangeLogs.]