From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Tue, 02 Aug 2011 11:13:48 -0400 [thread overview]
Message-ID: <jwvd3gn7syx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3fwlrz6fj.fsf@stories.gnus.org>
> I think the most pleasant way to do this would be to add a slightly more
> formal Maintainer: syntax. Grepping though the sources, we find stuff
> like:
> vt-control.el:6:;; Maintainer: Rob Riepel <riepel@networking.stanford.edu>
> whitespace.el:6:;; Maintainer: Vinicius Jose Latorre <viniciusjl@ig.com.br>
> wid-edit.el:6:;; Maintainer: FSF
> window.el:6:;; Maintainer: FSF
> woman.el:6:;; Maintainer: FSF
> x-dnd.el:6:;; Maintainer: FSF
> xml.el:6:;; Maintainer: Mark A. Hershberger <mah@everybody.org>
> calc/calc-aent.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calcalg2.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calcalg3.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-alg.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-arith.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> calc/calc-bin.el:6:;; Maintainer: Jay Belanger <jay.p.belanger@gmail.com>
> My suggestion would be to change this to
> ;; Package-maintainer: calc:Jay Belanger <jay.p.belanger@gmail.com>
I don't think we need a new syntax.
We do need to improve the values we set there. But basically "FSF"
means that the maintainer reads bug-gnu-emacs, and anything else should
mean "I want to receive notifications about commits and pending bugs".
We could add some way to put the email address while at the same time
requesting "please don't auto-send notifications" (for those who
already read bug-gnu-emacs but don't want to mark their package as
maintained by "FSF").
If file foo-bar.el has no Maintainer, then we should defer to the
maintainer of the file foo.el.
If someone could set this up for commits in trunk and in ELPA (where
the Maintainer field should always be provided).
Stefan
prev parent reply other threads:[~2011-08-02 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 22:48 Maintainer overview Lars Magne Ingebrigtsen
2011-07-28 2:55 ` Eli Zaretskii
2011-07-28 7:35 ` Lars Magne Ingebrigtsen
2011-07-28 7:57 ` Eli Zaretskii
2011-07-28 8:09 ` Lars Magne Ingebrigtsen
2011-07-28 9:05 ` Eli Zaretskii
2011-07-28 9:08 ` Lars Magne Ingebrigtsen
2011-07-29 2:11 ` Stephen J. Turnbull
2011-07-28 8:48 ` Detlev Zundel
2011-07-28 11:23 ` Juanma Barranquero
2011-07-28 4:47 ` Jambunathan K
2011-07-28 6:14 ` Tim Cross
2011-07-28 7:11 ` Jambunathan K
2011-07-28 7:37 ` Lars Magne Ingebrigtsen
2011-07-28 8:23 ` Tim Cross
2011-07-28 9:04 ` Eli Zaretskii
2011-07-28 8:07 ` Bastien
2011-07-28 16:49 ` Chong Yidong
2011-07-29 11:22 ` Lars Magne Ingebrigtsen
2011-08-02 15:13 ` Stefan Monnier [this message]
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=jwvd3gn7syx.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 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).