From: Xue Fuqiao <xfq.free@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel <emacs-devel@gnu.org>, Tassilo Horn <tsdh@gnu.org>
Subject: Re: admin/MAINTAINERS
Date: Tue, 29 Sep 2015 08:21:50 +0800 [thread overview]
Message-ID: <CAAF+z6EermAvO7x_=CSXqxcB4821+=UNAi3GFqmhCCie-Wq=_Q@mail.gmail.com> (raw)
In-Reply-To: <CAAF+z6HZfhTdPpb9Fr_iO8e5oMxQWS+03LZTpaw7KO8nv7ZKXQ@mail.gmail.com>
his -> Michael's
On Tue, Sep 29, 2015 at 8:20 AM, Xue Fuqiao <xfq.free@gmail.com> wrote:
> On Mon, Sep 28, 2015 at 3:58 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Tassilo Horn <tsdh@gnu.org>
>>> Cc: emacs-devel@gnu.org
>>> Date: Mon, 28 Sep 2015 09:41:32 +0200
>>>
>>> I just added an entry for doc-view (myself) and the RefTeX files where I
>>> have written "The GNU AUCTeX Maintainers". I guess such
>>> non-single-person entries are ok, right?
>>
>> It's OK, but would it make sense to add some information about who
>> those maintainers are, or how/where to reach them? I mean, suppose
>> we'd need to ask them something, how would we go about writing to
>> them?
>
> What about also adding contact information for single-person entries?
> So, suppose I'd need to ask something about Tramp, if there's contact
> information in admin/MAINTAINERS, then I don't need to find his email
> address in ChangeLog files or other places.
next prev parent reply other threads:[~2015-09-29 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 9:39 admin/MAINTAINERS Eli Zaretskii
2015-09-28 7:41 ` admin/MAINTAINERS Tassilo Horn
2015-09-28 7:58 ` admin/MAINTAINERS Eli Zaretskii
2015-09-28 9:00 ` admin/MAINTAINERS Tassilo Horn
2015-09-28 9:25 ` admin/MAINTAINERS Eli Zaretskii
2015-09-29 0:20 ` admin/MAINTAINERS Xue Fuqiao
2015-09-29 0:21 ` Xue Fuqiao [this message]
2015-09-29 5:15 ` admin/MAINTAINERS Eli Zaretskii
2015-09-29 11:24 ` admin/MAINTAINERS Artur Malabarba
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='CAAF+z6EermAvO7x_=CSXqxcB4821+=UNAi3GFqmhCCie-Wq=_Q@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tsdh@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 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.