From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: John Darrington <john@darrington.wattle.id.au>
Subject: Re: [PATCH 1/2] GDB: S12Z: Add assertion
Date: Sun, 18 Nov 2018 18:42:00 -0000 [thread overview]
Message-ID: <20181118114242.675f5f14@pinnacle.lan> (raw)
In-Reply-To: <20181118092258.wmiltm7lfzj2cvnw@jocasta.intra>
On Sun, 18 Nov 2018 10:22:58 +0100
John Darrington <john@darrington.wattle.id.au> wrote:
> On Sat, Nov 17, 2018 at 02:59:28PM -0700, Kevin Buettner wrote:
>
> > ---
> > gdb/s12z-tdep.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/gdb/s12z-tdep.c b/gdb/s12z-tdep.c
> > index 79f5772035..bd0bd7c001 100644
> > --- a/gdb/s12z-tdep.c
> > +++ b/gdb/s12z-tdep.c
> > @@ -320,6 +320,7 @@ s12z_frame_cache (struct frame_info *this_frame, void **prologue_cache)
> > }
> > else
> > {
> > + gdb_assert (this_sp == this_sp_for_id);
> > /* The stack pointer of the prev frame is frame_size greater
> > than the stack pointer of this frame plus one address
> > size (caused by the JSR or BSR). */
> > --
>
> Could you please add a ChangeLog entry?
>
> Also, on the same topic, what happened to the ChangeLog entries
> for the initial commit / push of the s12z port? (I don't see them
> in the ChangeLog file.)
>
> Is it really necessary in 2018 to have ChangeLogs? After all, the same
> information is available by typing git log and/or git diff. If the answer is
> "yes", then how about generating it automatically using the git-log-to-changelog
> script which is available in gnulib ? Many other projects have gone over to
> this method.
>
> ChangeLogs are a dreaded nuisance. They are almost guaranteed to cause merge
> conflicts. The information they contain is redundant. Their formatting
> requirements are onerous. And in thirty years of software development, I don't
> think I've ever experienced a case where I've needed to refer to one.
While I agree with some of your arguments against the use of
ChangeLogs in 2018, the GDB project still requires the use of
ChangeLogs. See:
https://sourceware.org/gdb/wiki/ContributionChecklist#ChangeLog
and:
https://sourceware.org/gdb/wiki/ContributionChecklist#Properly_Formatted_GNU_ChangeLog
And, FWIW, the first thing that I did while reviewing your patches was
to look at the current ChangeLog to get a brief history of changes to
s12z-tdep.c. I was surprised when I did not find any ChangeLog entries,
though I did figure it out by consulting the git log.
Kevin
next prev parent reply other threads:[~2018-11-18 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 9:18 John Darrington
2018-11-12 9:18 ` [PATCH 2/2] GDB: S12Z: new function s12z_extract_return_value John Darrington
2018-11-18 6:35 ` Kevin Buettner
2018-11-18 9:13 ` John Darrington
2018-11-18 18:28 ` Kevin Buettner
2018-11-20 7:56 ` [PATCH] " John Darrington
2018-11-20 16:40 ` Kevin Buettner
2018-11-20 17:01 ` John Darrington
2018-11-17 21:59 ` [PATCH 1/2] GDB: S12Z: Add assertion Kevin Buettner
2018-11-18 9:23 ` John Darrington
2018-11-18 18:42 ` Kevin Buettner [this message]
2018-11-19 16:09 ` Joel Brobecker
2018-11-19 16:47 ` [PATCH] " John Darrington
2018-11-20 5:16 ` Kevin Buettner
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=20181118114242.675f5f14@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=john@darrington.wattle.id.au \
/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