From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116379: Replace "Maintainer: FSF" with the emacs-devel mailing address
Date: Mon, 10 Feb 2014 14:23:19 -0500 [thread overview]
Message-ID: <1psirqojq0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwv38jq3i1a.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Mon, 10 Feb 2014 14:08:24 -0500")
Stefan Monnier wrote:
> For files included in Emacs, then I don't see a need to include extra
> references to emacs-devel@gnu.org (just like we don't have such in the
> C files).
Fine, let's bikeshed this to death.
"emacs-devel@gnu.org" is obviously (to me) better than "FSF".
If you've got something better than "emacs-devel", feel free.
> For files in ELPA, emacs-devel@gnu.org isn't right either: the
> maintainer address is where the commit-script sends a copy of the diff,
> and I don't think we don't want to send those to emacs-devel@gnu.org.
Then the commit script (which is currently broken anyway, according to
http://debbugs.gnu.org/16435) should special-case emacs-devel and ignore
it.
Ironically, the forward-diffs script itself, which I wrote and have
abandoned because of git, is the only thing in elpa that uses such a
Maintainer heading, so it's a non-problem AFAICS.
next prev parent reply other threads:[~2014-02-10 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WCfma-0005gV-3S@vcs.savannah.gnu.org>
2014-02-10 17:05 ` [Emacs-diffs] trunk r116379: Replace "Maintainer: FSF" with the emacs-devel mailing address Stefan Monnier
2014-02-10 17:12 ` Glenn Morris
2014-02-10 18:17 ` Ted Zlatanov
2014-02-10 18:20 ` Glenn Morris
2014-02-11 19:11 ` Richard Stallman
2014-02-10 19:08 ` Stefan Monnier
2014-02-10 19:23 ` Glenn Morris [this message]
2014-02-10 19:31 ` Eli Zaretskii
2014-02-10 23:13 ` Bastien
2014-02-10 23:38 ` Glenn Morris
2014-02-11 19:04 ` Achim Gratz
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=1psirqojq0.fsf@fencepost.gnu.org \
--to=rgm@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 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.