unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master bef1be8: Fixes for "Maintainer:" and related lines
Date: Wed, 22 May 2019 18:19:50 -0400	[thread overview]
Message-ID: <ock1eiyvw9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <22fdcee1-39b7-fea0-b68c-73de4167a5c5@cs.ucla.edu> (Paul Eggert's message of "Mon, 20 May 2019 08:39:34 -0700")

Paul Eggert wrote:

> However, that node doesn't match existing practice as it goes on to
> say, "Some files in Emacs use 'FSF' for the maintainer.  This means
> that the original author is no longer responsible for the file, and
> that it is maintained as part of Emacs" despite the fact that no files
> in the Emacs source code use "FSF" for the maintainer (either before
> or after my recent patch).

I changed it to use a real email address in 34dc21d.
It seemed harmless to leave the explanation of FSF, for older files
people might encounter. (Or more likely I forgot to remove it.)

> it's quite common to see comment pairs like the following, which are
> the first five remaining instances of "Maintainer:" lines in Emacs's
> .el files (sorted by file name):
>
> ;; Author: Markus Rost <markus.rost@mathematik.uni-regensburg.de>
> ;; Maintainer: Markus Rost <rost@math.ohio-state.edu>

Harmless duplication that does not contravene the convention.

> All in all I think it'd lessen confusion and simplify maintenance if
> we used "Maintainer:" for contacting current maintainers who aren't
> authors and don't normally read bug reports. Something like the
> attached proposed patch, say?

That's an incompatible change. If I see a file with only an Author
header, I can't tell whether it follows the old convention (author is
the maintainer), or the new one (emacs-devel is the maintainer).

My counter suggestion is to revert bef1be8.



  reply	other threads:[~2019-05-22 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190520043434.1198.8439@vcs0.savannah.gnu.org>
     [not found] ` <20190520043437.4F9A82068F@vcs0.savannah.gnu.org>
2019-05-20 14:40   ` master bef1be8: Fixes for "Maintainer:" and related lines Glenn Morris
2019-05-20 15:39     ` Paul Eggert
2019-05-22 22:19       ` Glenn Morris [this message]
2019-05-25 21:34         ` Paul Eggert

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=ock1eiyvw9.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).