Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] Make cu/tu functions in dwarf.exp take a list of options
Date: Mon, 20 May 2013 16:42:00 -0000	[thread overview]
Message-ID: <CADPb22REnvL1=HH281V8aQ+2z+1rawqG=R25mLdfn=XL+shzdQ@mail.gmail.com> (raw)
In-Reply-To: <20130520054023.GL4017@adacore.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.]


  reply	other threads:[~2013-05-20 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 17:28 Doug Evans
2013-05-17 18:04 ` Tom Tromey
2013-05-17 18:20   ` Doug Evans
2013-05-20  5:40     ` Joel Brobecker
2013-05-20 16:42       ` Doug Evans [this message]
2013-05-20 22:09   ` Doug Evans

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='CADPb22REnvL1=HH281V8aQ+2z+1rawqG=R25mLdfn=XL+shzdQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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