all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Omitting "Maintainer:"
Date: Sun, 19 May 2019 12:44:55 -0400	[thread overview]
Message-ID: <jwvzhnimm7d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 2807078f-19a8-4648-3c65-31772934171c@cs.ucla.edu

> useless, and the remaining "Maintainer:" instances are easily (and
> more-accurately) determined from the commit logs. If we had removed

Well, that depends: in many files, the commit log has loads of cosmetic
commits from other people than the maintainer, so it's good to have an
official statement about who considers himself in charge.

Also, the `Maintainer:` line can specify a mailing-list or a "virtual"
email, whereas commits usually specify the personal email of
a given individual.

This said, I agree that whether the "Maintainer: emacs-devel.." are
useful is debatable.


        Stefan




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 12:42 Robert J. Chassel reference in Intro to Emacs Lisp Jean-Christophe Helary
2019-05-18 13:15 ` Richard Copley
2019-05-18 14:03   ` Jean-Christophe Helary
2019-05-18 14:31     ` Jean-Christophe Helary
2019-05-18 18:08       ` Paul Eggert
2019-05-18 21:41         ` Richard Stallman
2019-05-19  1:55           ` Jean-Christophe Helary
2019-05-19 16:32           ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) Paul Eggert
2019-05-19 16:44             ` Stefan Monnier [this message]
2019-05-19 17:02               ` Omitting "Maintainer:" Eli Zaretskii
2019-05-19 19:18             ` Lars Ingebrigtsen
2019-05-20  4:38               ` Paul Eggert
2019-05-19 20:47             ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) 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=jwvzhnimm7d.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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.