From: Luis Machado <luis.machado@linaro.org>
To: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: sim: replacing ChangeLog files with online git logs
Date: Wed, 31 Mar 2021 08:35:54 -0300 [thread overview]
Message-ID: <b5e9da4e-496b-e6db-7712-21a6f33646bf@linaro.org> (raw)
In-Reply-To: <20210331032728.GJ11111@adacore.com>
Hi Joel,
On 3/31/21 12:27 AM, Joel Brobecker wrote:
> Hi Mike,
>
>>>>> No the second proposes to replace the current ChangeLog with one
>>>>> auto-generated upon release.
>>>>>
>>>>> This ChangeLog would in effect be a reformatted `git log` output.
>>>>
>>>> I don't object to that, either. The question is: what we will require
>>>> the Git log messages to contain then? Currently, the entire ChangeLog
>>>> entry goes there, but once the manually written ChangeLog files are
>>>> retired, what will remain? That was the crux of the recent
>>>> discussion.
>>>
>>> we won't require the ChangeLog-like entries in the commit message for sim/.
>>> the generated ChangeLog will have name+date+git log.
>>
>> i wanted to give time for people to respond & post any thoughts that they
>> might have lingering before i moved forward. since things have gone quiet
>> now, i guess we've reached the end? so i'll give another few days before
>> i land the change for sim/.
>
> Can you hold off on this for now? We're discussing it within the group
> of GDB Global Maintainers, and we need more time to converge.
>
Out of curiosity, is the discussion specifically focused on sim/ or
should we address the bigger issue of ChangeLog's within the GDB codebase?
next prev parent reply other threads:[~2021-03-31 11:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 2:53 Mike Frysinger
2021-03-13 7:30 ` Eli Zaretskii
2021-03-13 15:12 ` Mike Frysinger
2021-03-13 16:02 ` Eli Zaretskii
2021-03-13 16:26 ` Mike Frysinger
2021-03-13 16:38 ` Eli Zaretskii
2021-03-13 18:21 ` Mike Frysinger
2021-03-13 18:32 ` Eli Zaretskii
2021-03-17 6:07 ` Mike Frysinger
2021-03-17 13:14 ` Eli Zaretskii
2021-03-17 14:31 ` Luis Machado
2021-03-17 14:47 ` Eli Zaretskii
2021-03-17 14:52 ` Luis Machado
2021-03-17 15:09 ` Eli Zaretskii
2021-03-17 15:22 ` Luis Machado
2021-03-17 15:40 ` Eli Zaretskii
2021-03-17 15:52 ` Simon Marchi
2021-03-17 16:09 ` Eli Zaretskii
2021-03-17 17:24 ` Luis Machado
2021-03-17 17:53 ` Eli Zaretskii
2021-03-17 20:53 ` Luis Machado
2021-03-18 9:31 ` Andrew Burgess
2021-03-18 9:48 ` Eli Zaretskii
2021-03-22 2:19 ` Maciej W. Rozycki
2021-03-22 3:38 ` Eli Zaretskii
2021-03-23 4:57 ` Mike Frysinger
2021-03-23 5:05 ` Mike Frysinger
2021-03-23 11:06 ` Andrew Burgess
2021-03-24 3:45 ` Mike Frysinger
2021-03-24 16:46 ` Eli Zaretskii
2021-03-24 16:59 ` Andrew Burgess
2021-03-24 17:39 ` Eli Zaretskii
2021-03-24 18:44 ` Mike Frysinger
2021-03-31 2:27 ` Mike Frysinger
2021-03-31 3:27 ` Joel Brobecker
2021-03-31 11:35 ` Luis Machado [this message]
2021-03-31 15:29 ` Joel Brobecker
2021-04-01 3:41 ` Mike Frysinger
2021-04-19 0:52 ` Mike Frysinger
2021-04-19 2:32 ` Joel Brobecker
2021-04-19 4:31 ` Mike Frysinger
2021-04-19 5:00 ` Joel Brobecker
2021-05-23 3:26 ` Mike Frysinger
2021-06-10 12:11 ` Luis Machado
2021-03-13 18:34 ` Paul Smith
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=b5e9da4e-496b-e6db-7712-21a6f33646bf@linaro.org \
--to=luis.machado@linaro.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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).