unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 62813@debbugs.gnu.org
Subject: bug#62813: 29.0.60; etc/AUTHORS listing README.md
Date: Thu, 13 Apr 2023 17:45:09 +0300	[thread overview]
Message-ID: <83r0sn4z9m.fsf@gnu.org> (raw)
In-Reply-To: <87y1mwkog1.fsf@posteo.net> (message from Philip Kaludercic on Thu, 13 Apr 2023 11:32:14 +0000)

tags 62813 notabug
thanks

> From: Philip Kaludercic <philipk@posteo.net>
> Date: Thu, 13 Apr 2023 11:32:14 +0000
> 
> When viewing etc/AUTHORS, I see that a number of people have modified a
> file "README.md" that is not to be found in emacs.git.  From what I see,
> these people have frequently also changed eglot.git, which makes me
> think that this is an issue with the import-merge of the Eglot
> repository into emacs.git.  This seems like something that authors.el
> should be made aware of.

First, attributions in AUTHORS don't necessarily mention files that
are physically present in the repository.  E.g., we don't want to
ignore contributions to files that we at some point decided to remove
from Emacs.

In this case, it was my decision to tweak authors.el's databases so
that contributions to files in merged packages, such as Eglot and
use-package, will be reflected in AUTHORS even though the files to
which they contributed were eventually deleted when the package was
merged.  Where the stuff in those deleted files was moved to other
files, which do exist, I tried to redirect the attributions to the
existing files.  But where that was impossible or impractical, I saw
no problem in having removed files referenced by AUTHORS.

Eglot's README.md was deleted some time after Eglot was merged with
Emacs, or maybe even before that, but the text in it is now largely in
the Eglot manual, in some form or another.  So having these
attributions in AUTHORS makes sense to me.

This is not a bug.





  reply	other threads:[~2023-04-13 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 11:32 bug#62813: 29.0.60; etc/AUTHORS listing README.md Philip Kaludercic
2023-04-13 14:45 ` Eli Zaretskii [this message]
2023-09-03 10:36   ` Stefan Kangas

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=83r0sn4z9m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62813@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    /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).