unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Emacs developers <emacs-devel@gnu.org>
Cc: 21998@debbugs.gnu.org
Subject: bug#21998: Is it time to drop ChangeLogs? (Was: bug#21998: Run 'make change-history' on release branch)
Date: Sun, 6 Mar 2016 14:34:12 -0800	[thread overview]
Message-ID: <56DCB064.9060206__10704.1455958553$1457303721$gmane$org@cs.ucla.edu> (raw)
In-Reply-To: <m2oaarxojf.fsf_-_@newartisans.com>

John Wiegley wrote:
> What do you all think about ChangeLogs, and their value
> to you in your work on Emacs?

I regularly do the equivalent of:

grep PATTERN $(git ls-files | grep -v ChangeLog)

That is, in searches I typically ignore ChangeLog* files because of their 
less-useful chatter. I'd be happy if we stopped maintaining these files in the 
master branch (we should keep them for emacs-25). I'd be happy if we removed the 
existing ChangeLog* files from the master branch.

Even if we remove ChangeLogs, we should still have guidelines for commit message 
format, as saying "anything goes" would make it harder to read the output of 
'git log'. I don't mind using ChangeLog format in commit messages, as it's a 
well-understood format and switching to some other format could well be more 
trouble than it's worth.





  parent reply	other threads:[~2016-03-06 22:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 19:08 bug#21998: Run 'make change-history' on release branch Glenn Morris
2016-02-13  0:52 ` Paul Eggert
2016-02-16 16:41   ` Glenn Morris
2016-02-16 17:54     ` Paul Eggert
2016-03-04 16:46     ` Glenn Morris
2016-03-05 19:11       ` Eli Zaretskii
2016-03-06  9:47         ` Lars Magne Ingebrigtsen
2016-03-06 18:02           ` Dmitry Gutov
2016-03-06 21:07           ` John Wiegley
2016-03-06 21:25             ` Ingo Lohmar
2016-03-06 21:52               ` bug#21998: Is it time to drop ChangeLogs? (Was: bug#21998: Run 'make change-history' on release branch) John Wiegley
     [not found]               ` <m2oaarxojf.fsf_-_@newartisans.com>
2016-03-06 22:05                 ` Eric S. Raymond
2016-03-06 22:34                 ` Paul Eggert [this message]
2016-03-06 23:06                 ` Drew Adams
     [not found]                 ` <64a52598-ad53-498c-993c-67d7827dbdfc@default>
2016-03-07  0:15                   ` bug#21998: Is it time to drop ChangeLogs? John Wiegley
     [not found]                   ` <m2io0zw3cd.fsf@newartisans.com>
2016-03-07  0:24                     ` Drew Adams
2016-03-07  0:22                 ` Mathieu Lirzin
     [not found]                 ` <87vb4zb0i4.fsf@gnu.org>
2016-03-07  1:19                   ` Eric S. Raymond
2016-03-07  9:29                 ` Alan Mackenzie
     [not found]                 ` <56DCB064.9060206@cs.ucla.edu>
2016-03-07 16:26                   ` bug#21998: Is it time to drop ChangeLogs? (Was: bug#21998: Run 'make change-history' on release branch) Eli Zaretskii
2016-03-08  7:32         ` bug#21998: Run 'make change-history' on release branch Glenn Morris
2016-03-08 16:08           ` Eli Zaretskii
2016-03-07  6:51       ` Richard Stallman
2016-03-07 16:02         ` Eli Zaretskii
2016-03-07 16:35           ` John Wiegley
2016-03-07 17:00             ` Eli Zaretskii
2016-03-07 17:51               ` John Wiegley
2016-03-08 18:23           ` Richard Stallman
2016-03-08 18:30             ` Eli Zaretskii
2016-03-09 16:38               ` Richard Stallman
2016-03-09 16:51                 ` Eli Zaretskii
2016-03-10 21:23                   ` Richard Stallman
2016-03-11  8:48                     ` Eli Zaretskii
2016-03-11 10:05       ` Nicolas Petton

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='56DCB064.9060206__10704.1455958553$1457303721$gmane$org@cs.ucla.edu' \
    --to=eggert@cs.ucla.edu \
    --cc=21998@debbugs.gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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).