public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@linaro.org>
Cc: vapier@gentoo.org, gdb@sourceware.org
Subject: Re: sim: replacing ChangeLog files with online git logs
Date: Wed, 17 Mar 2021 17:09:32 +0200	[thread overview]
Message-ID: <83o8fhddg3.fsf@gnu.org> (raw)
In-Reply-To: <bbc6fd38-3f1d-d13a-d3ab-6bfaf8a1504b@linaro.org> (message from Luis Machado on Wed, 17 Mar 2021 11:52:03 -0300)

> Cc: vapier@gentoo.org, gdb@sourceware.org
> From: Luis Machado <luis.machado@linaro.org>
> Date: Wed, 17 Mar 2021 11:52:03 -0300
> 
> > That's the idea, yes.  Of course, for such a generated ChangeLog to be
> > useful, the Git commit log messages should be informative enough.
> 
> I see. Given the ChangeLog will list all the files that were changed, I 
> suppose the commit messages would only need to describe what the changes 
> are about. But the description may not list function names, files, new 
> data structures etc. Would that work?
> 
> Or did you have something more specific in mind?

Ideally, the commit log messages should provide the same information
as the manually managed ChangeLog files, in which case generating the
files from Git log at release time doesn't lose any information.  If
some of that information is missing from the Git logs, then the
generated ChangeLog files will be somewhat less useful.  But if the
project doesn't require to record more than that in Git log messages,
then it's the problem with the Git logs, not with ChangeLogs.

For example, in Emacs we ask contributors to format the Git log
messages according to ChangeLog format, and then the generated
ChangeLog file looks exactly like the manual one would.

  reply	other threads:[~2021-03-17 15:09 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 [this message]
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
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=83o8fhddg3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@linaro.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).