From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org,Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Omitting "Maintainer:"
Date: Sun, 19 May 2019 18:02:34 +0100 [thread overview]
Message-ID: <23FF5754-BBD6-4BD1-92F7-8DA81D8EF5C9@gnu.org> (raw)
In-Reply-To: <jwvzhnimm7d.fsf-monnier+emacs@gnu.org>
On May 19, 2019 5:44:55 PM GMT+01:00, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > 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
FWIW, I use that line to know whom to ping or consult about a given file.
next prev parent reply other threads:[~2019-05-19 17:02 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 ` Omitting "Maintainer:" Stefan Monnier
2019-05-19 17:02 ` Eli Zaretskii [this message]
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
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=23FF5754-BBD6-4BD1-92F7-8DA81D8EF5C9@gnu.org \
--to=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).