From: Joel Brobecker <brobecker@adacore.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] GDB: S12Z: Add assertion
Date: Mon, 19 Nov 2018 16:09:00 -0000 [thread overview]
Message-ID: <20181119160941.GB3276@adacore.com> (raw)
In-Reply-To: <20181118114242.675f5f14@pinnacle.lan>
Hey John,
To add to what Kevin said, we've been discussing this topic many times.
I am pretty sure most people would be very happy to be getting rid of
ChangeLog entries. I think the main issue, now, is to automate their
generation when producing the source packages and releases; this is
because we are a GNU project, and we are expected to allow people
without the git repository to have a sense of the changes that were
made. I think that if we have a process in place that automates this,
we should be OK to replace the ChangeLog files by data extracted from
the revision logs.
What we need, at this point, is someone sufficiently motivated to
put in place this automatic generation. We might also need a bit of
development work on the hooks to validate the revision log's format
and confirm that it always contains a ChangeLog entry in a format
we can understand so we can always extract it (I can take care of
that part once we have an agreement on the process).
--
Joel
next prev parent reply other threads:[~2018-11-19 16:09 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
2018-11-19 16:09 ` Joel Brobecker [this message]
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=20181119160941.GB3276@adacore.com \
--to=brobecker@adacore.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