All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers
Date: Tue, 13 May 2014 09:32:00 -0600	[thread overview]
Message-ID: <53723AF0.704@wwwdotorg.org> (raw)
In-Reply-To: <2841648.YvDH29bsdC@avalon>

On 05/13/2014 09:11 AM, Laurent Pinchart wrote:
...
> Wouldn't it help if we could write down whatever rules that each subsystem 
> maintainer found best ? For instance some maintainers expect to be CC'ed on 
> patch submission, other prefer not to be CC'ed. When sending a patch to a new 
> subsystem developers currently have no easy way to find this kind of 
> information.

Well, get_maintainers.pl spits out the list of destination email
addresses to send to. It should be easy enough to augment MAINTAINERS
entries with a flag (or different tag type) to say "I'm the maintainer
of this area, but I don't want to be CC'd on the email; just send it to
the list and I'll see it.", and have get_maintainers.pl print out that
information.

  reply	other threads:[~2014-05-13 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 13:27 [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers Takashi Iwai
2014-05-13 14:31 ` Jiri Kosina
2014-05-13 14:55   ` Takashi Iwai
2014-05-13 14:57   ` Sarah A Sharp
2014-05-13 15:11     ` Laurent Pinchart
2014-05-13 15:32       ` Stephen Warren [this message]
2014-05-13 16:28     ` josh
2014-05-13 16:53       ` Olof Johansson
2014-05-13 18:06       ` Jiri Kosina
2014-05-13 19:02       ` Mark Brown
2014-05-16  3:18       ` Jason Cooper
2014-05-18 15:09       ` Mauro Carvalho Chehab
2014-05-20 16:06         ` Josh Triplett
2014-05-23  8:02       ` Linus Walleij

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=53723AF0.704@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    /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.
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.