Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: switch to autogenerated ChangeLog files
Date: Tue, 12 Jan 2021 16:27:04 -0500	[thread overview]
Message-ID: <20210112212704.GZ7494@vapier> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2101121805370.1193382@digraph.polyomino.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]

On 12 Jan 2021 18:14, Joseph Myers wrote:
> On Tue, 12 Jan 2021, Andrew Burgess wrote:
> > > to be clear, it isn't generating entries exactly like we write.  it's
> > > using the git commit logs with formatted dates.  so i don't think this
> > > applies exactly anymore.  so it's inline with the GNU's VCS principles:
> > > https://www.gnu.org/prep/standards/html_node/Change-Logs.html
> > > (and that also recommends just using gitlog-to-changelog).
> > 
> > I read this page, and especially the part that talks about using
> > gitlog-to-changelog, and I don't find their argument compelling.
> 
> What the GNU Coding Standards say about ChangeLogs isn't what would make 
> sense from a starting point of modern development practices, it's what we 
> could convince the maintainers of the GNU Coding Standards (being used to 
> ChangeLog-centric development practices) to allow.
> 
> The discussion started at 
> <https://lists.gnu.org/archive/html/bug-standards/2017-07/msg00000.html> 
> and took a few years (a few bits were on an internal GNU Project list, but 
> most was on bug-standards).  In particular, the maintainers of the GNU 
> Coding Standards fixated on a point that they were used to using the lists 
> of changes to named entities (functions etc.) in ChangeLogs as part of the 
> debugging process, while my position is that the typical problem for which 
> such lists are used is not "map a commit to the named entities modified in 
> that change" but the inverse problem "map a named entity to the commits 
> changing it", which version control tools handle well without needing to 
> go via the ChangeLog-format lists at all.

thanks for the background info.  tbh, i'm just trying to find any authority
that i can appeal to to help convince people to autogenerate things and not
require manual creation :).
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-01-12 21:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10  3:37 [PATCH 1/3] src-release: fix indentation Mike Frysinger via Gdb-patches
2021-01-10  3:37 ` [PATCH 2/3] gnulib: import gitlog-to-changelog Mike Frysinger via Gdb-patches
2021-01-11 11:06   ` Andrew Burgess
2021-01-10  3:42 ` [PATCH] sim: switch to autogenerated ChangeLog files Mike Frysinger via Gdb-patches
2021-01-11 11:05   ` Andrew Burgess
2021-01-11 17:00     ` Simon Marchi via Gdb-patches
2021-01-11 17:10       ` Luis Machado via Gdb-patches
2021-01-11 17:31         ` Christian Biesinger via Gdb-patches
2021-01-11 19:38       ` Mike Frysinger via Gdb-patches
2021-01-11 19:54         ` Simon Marchi via Gdb-patches
2021-01-11 20:35           ` Mike Frysinger via Gdb-patches
2021-01-12 10:47         ` Andrew Burgess
2021-01-12 18:14           ` Joseph Myers
2021-01-12 18:27             ` Eli Zaretskii via Gdb-patches
2021-01-12 18:40               ` Eli Zaretskii via Gdb-patches
2021-01-12 21:27             ` Mike Frysinger via Gdb-patches [this message]
2021-01-12 21:22           ` Mike Frysinger via Gdb-patches
2021-03-09  5:51           ` Mike Frysinger via Gdb-patches
2021-03-09  9:42             ` Andrew Burgess
2021-03-17 14:22               ` Luis Machado via Gdb-patches
2021-01-12 23:20 ` [PATCH 1/3] src-release: fix indentation Mike Frysinger via Gdb-patches

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=20210112212704.GZ7494@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --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