From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Thu, 28 Jul 2011 09:37:50 +0200 [thread overview]
Message-ID: <m3tya6vos1.fsf@stories.gnus.org> (raw)
In-Reply-To: CAC=50j_h2aUuwXHZkVK3d411q-g4-ESwyE4GbxHOeLXxqaWbuw@mail.gmail.com
Tim Cross <theophilusx@gmail.com> writes:
> That sounds like useful improvements. However, can I suggest
> abstracting the contact details another layer. Some maintainers may
> not like their email being distributed inside emacs source files and
> when that maintainer leaves or someone else takes over maintenance,
> the information becomes outdated.
If your email address is secret, then you can't participate in Emacs
development. So I think the first consideration is irrelevant.
The second is true, but this information is for Emacs developers who
want to know where bugs should be reassigned. These people presumably
have an updated Emacs, so it isn't particularly relevant for them,
either.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-28 7:37 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 [this message]
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
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=m3tya6vos1.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--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).