From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: emacs-devel@gnu.org
Subject: Re: I'm working on getting the pretest out, but...
Date: Thu, 05 Oct 2017 11:31:46 +0300 [thread overview]
Message-ID: <83bmlmxafh.fsf@gnu.org> (raw)
In-Reply-To: <8760bu3ak8.fsf@petton.fr> (message from Nicolas Petton on Wed, 04 Oct 2017 22:47:03 +0200)
> From: Nicolas Petton <nicolas@petton.fr>
> Cc: eliz@gnu.org
> Date: Wed, 04 Oct 2017 22:47:03 +0200
>
> I'm fixing errors in ChangeLog entries one by one (there are more than
> 200), which is a bit tedious.
Thank you for your efforts.
> This problem seems to reoccur for each first pretest of a major
> release. Many commit messages have wrong file paths, which is an easy
> mistake to make since there's no check being performed (Magit and VC
> can help with that though).
>
> There's already a pre-commit hook that does some checks on ChangeLog
> entries, and I was thinking that maybe we could extend it to check for
> the existence of file paths referenced in commit messages.
That could be a good idea, IMO.
> Another problem I'm facing is author names. I get 30 ignored authors
> when updating etc/AUTHORS. Some of them are easy to fix given that they
> are known contributors.
>
> To my surprise however, some of these names refer to old commits (1998
> being the oldest). I don't remember having this issue in the past,
> which is weird, and I'm wondering what to do with these ChangeLog
> entries.
Can you show those problematic author names?
next prev parent reply other threads:[~2017-10-05 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 20:47 I'm working on getting the pretest out, but Nicolas Petton
2017-10-05 3:16 ` Stefan Monnier
2017-10-05 8:31 ` Eli Zaretskii [this message]
2017-10-05 21:14 ` Nicolas Petton
2017-10-06 9:43 ` Eli Zaretskii
2017-10-06 15:16 ` Richard Stallman
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=83bmlmxafh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
/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.