unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: emacs-devel@gnu.org
Subject: Re: Maintainer overview
Date: Thu, 28 Jul 2011 10:48:33 +0200	[thread overview]
Message-ID: <m2wrf294f2.fsf@ohwell.denx.de> (raw)
In-Reply-To: m3y5zivovh.fsf@stories.gnus.org

Hi,

>>> I think it would be very nice if we had such a list of
>>> packages/maintainers -- that was up-to-date.
>>
>> We have something in admin/MAINTAINERS.
>
> It's a starting point.

Just as a hint - the Linux kernel has a pretty good grasp on this topic
with the MAINTAINERS[1] file.  There's a script alongside it[2] which
can find maintainers even for a presented patch.  That helps _a lot_ to
automatically find the responsible people.

Of course in Emacs we could integrate that better, but comparable
functionality would be nice to have ;)

Cheers
  Detlev

[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=MAINTAINERS
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=scripts/get_maintainer.pl

-- 
There are two hard things in computer science: cache invalidation,
naming things, and off-by-one errors.




  parent reply	other threads:[~2011-07-28  8:48 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 [this message]
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

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=m2wrf294f2.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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).