all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, iarchivedmywholelife@gmail.com,
	68691@debbugs.gnu.org
Subject: bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format
Date: Sat, 27 Jan 2024 17:07:25 -0800	[thread overview]
Message-ID: <CADwFkmkzhWrKpC7BTv=RVJW_wX-TFxkNBdCZoSvQjJqW9EsiyA@mail.gmail.com> (raw)
In-Reply-To: <86r0i4bm0t.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> The reason we keep the ChangeLog format is that then the ChangeLog
> files generated from the Git logs and included in the release tarballs
> are useful on their own, without the need to use Git and have the
> repository cloned on the end user's machine.  Admittedly, systems
> where Emacs is installed but Git access to our repository is limited
> or non-existent are relatively rare these days, but they do exist (I
> personally have to work on such a system, FWIW).  Being able to grep
> the ChangeLog files locally is an advantage in those cases.

I'm not saying users that read them don't exist, I just think they're
rare.  My guess is that ChangeLog files are consulted far less often
than NEWS, and we know how often that happens.

But if we still consider these files useful, I think we could also
create them starting from something like `git log --stat', and then
generating the rest.  We wouldn't get a perfect result, perhaps, but we
could probably get 99 % of the way there if we really wanted to.

IOW, I think the question of distributing ChangeLog files could be
considered separately from their exact format.





  reply	other threads:[~2024-01-28  1:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 17:20 bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format No Wayman
2024-01-25 23:09 ` Stefan Kangas
2024-01-26  1:27   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-26 18:44     ` Jim Porter
2024-01-28  0:44     ` Stefan Kangas
2024-01-28  6:18       ` Eli Zaretskii
2024-01-28  7:21         ` Stefan Kangas
2024-01-28  7:33           ` Eli Zaretskii
2024-01-28  8:43           ` Juri Linkov
2024-01-26  7:18   ` Eli Zaretskii
2024-01-28  1:07     ` Stefan Kangas [this message]
2024-01-28  6:21       ` Eli Zaretskii
2024-01-28  7:26         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28  7:42           ` Eli Zaretskii
2024-01-28  9:04             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28  9:57               ` Eli Zaretskii

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='CADwFkmkzhWrKpC7BTv=RVJW_wX-TFxkNBdCZoSvQjJqW9EsiyA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=68691@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=iarchivedmywholelife@gmail.com \
    --cc=luangruo@yahoo.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.