From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: vapier@gentoo.org, gdb@sourceware.org
Subject: Re: sim: replacing ChangeLog files with online git logs
Date: Wed, 24 Mar 2021 19:39:24 +0200 [thread overview]
Message-ID: <83lfacjvsj.fsf@gnu.org> (raw)
In-Reply-To: <20210324165918.GA1683671@embecosm.com> (message from Andrew Burgess on Wed, 24 Mar 2021 16:59:18 +0000)
> Date: Wed, 24 Mar 2021 16:59:18 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Mike Frysinger <vapier@gentoo.org>, gdb@sourceware.org
>
> * Eli Zaretskii <eliz@gnu.org> [2021-03-24 18:46:38 +0200]:
>
> > > Date: Tue, 23 Mar 2021 23:45:24 -0400
> > > From: Mike Frysinger <vapier@gentoo.org>
> > > Cc: gdb@sourceware.org, Andrew Burgess <andrew.burgess@embecosm.com>
> > >
> > > Eli: those patches look OK to you too ?
> >
> > They just add the script to our repository, AFAICT, so I of course
> > have no objections.
>
> 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.
> For the simulator this would mean there would no longer be any file
> that contained output in the format as:
>
> * file.c (symbol): description.
Well, I personally will lament the loss of that information. It's up
toy you-all to decide how much does that weigh.
next prev parent reply other threads:[~2021-03-24 17:39 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 [this message]
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
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=83lfacjvsj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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).