From: Nicolas Petton <nicolas@petton.fr>
To: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Preparing for 24.5
Date: Sun, 01 Feb 2015 19:39:32 +0100 [thread overview]
Message-ID: <87vbjlfpcr.fsf@petton.fr> (raw)
In-Reply-To: <87y4ohfqa7.fsf@petton.fr>
Nicolas Petton <nicolas@petton.fr> writes:
>
> I have errors with M-x authors. Some files referenced in changelogs seem
> to be missing. Should I add all of the missing files to `authors-ignored-files' or
> should I try to track renamed files from commits and add them to
> `authors-renamed-files-alist'?
>
> The missing files are:
>
> .bzrignore
> info/dir
> notes/changelogs
> admin/notes/bugtracker
> admin/notes/tags
> notes/bzr
> notes/BRANCH
> gnus-coding.txt
> emulation/ws-mode.el
I figured out that some of these files were renamed, and added them to
`authors-renamed-files-alist'. Some others were just issues in
changelog entries that I simply fixed.
Now I still have an issue with the following 3 files, and I'm not sure
if they should just be ignored:
info/dir
notes/changelogs
gnus-coding.txt
Also, should I add a changelog entry when fixing the changelog itself?
Nico
--
Nicolas Petton
http://nicolas-petton.fr
next prev parent reply other threads:[~2015-02-01 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 16:10 Preparing for 24.5 Stefan Monnier
2015-01-30 16:21 ` Nicolas Petton
2015-01-30 16:25 ` Eli Zaretskii
2015-02-01 18:19 ` Nicolas Petton
2015-02-01 18:39 ` Nicolas Petton [this message]
2015-02-01 18:47 ` Eli Zaretskii
2015-02-04 1:17 ` Nicolas Petton
2015-02-04 3:46 ` Eli Zaretskii
2015-02-04 9:57 ` Nicolas Petton
2015-02-04 15:26 ` Eli Zaretskii
2015-02-04 16:39 ` Nicolas Petton
2015-02-05 16:20 ` Eli Zaretskii
2015-02-06 12:19 ` Nicolas Petton
2015-02-04 15:20 ` Stefan Monnier
2015-02-04 15:53 ` 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=87vbjlfpcr.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).