unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, rms@gnu.org, brandelune@gmail.com
Subject: Re: Omitting "Maintainer:"
Date: Sun, 19 May 2019 21:18:40 +0200	[thread overview]
Message-ID: <m3d0ke8d7z.fsf@gnus.org> (raw)
In-Reply-To: <2807078f-19a8-4648-3c65-31772934171c@cs.ucla.edu> (Paul Eggert's message of "Sun, 19 May 2019 09:32:43 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> Come to think of it, the "Maintainer:" comments are no longer worth
> the effort of keeping them up-to-date, now that we have a
> version-control system that keeps track of authors and committers
> automatically.

There's so much noise from cosmetic and routine updates in the version
control system that it's really helpful to have a Maintainer: line to
hint at who the real person in charge of the file is, in my opinion.

But the Maintainer: emacs-devel bits don't add much value.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  parent reply	other threads:[~2019-05-19 19:18 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
2019-05-19 19:18             ` Lars Ingebrigtsen [this message]
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=m3d0ke8d7z.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=brandelune@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).