public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Wu, Bryan" <bryan.wu@analog.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Mike Frysinger <vapier.adi@gmail.com>,
	Paul Mundt <lethal@linux-sh.org>, Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] Blackfin arch: add kdebug header file
Date: Tue, 27 Mar 2007 10:27:22 +0200	[thread overview]
Message-ID: <20070327082722.GC2031@uranus.ravnborg.org> (raw)
In-Reply-To: <1174974045.6966.26.camel@roc-desktop>

On Tue, Mar 27, 2007 at 01:40:45PM +0800, Wu, Bryan wrote:
> 
> Thanks for this guide line information. I will dig into it.
> 
> But in my experience, it is difficult to find right patch email
> receivers, even in the MAINTAINERS file. If there are 20 patch emails,
> we should find 20 email receivers at least and manually add them to the
> emails. This is terrible, right? Any idea?
The Cc: foo <bar@com> contained in the descrition is used to keep this info
when you found it first time.
The patchbombing tools starts to support it.

	Sam

  reply	other threads:[~2007-03-27  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 10:12 [PATCH -mm] Blackfin arch: add kdebug header file Wu, Bryan
2007-03-26 21:45 ` Arnd Bergmann
2007-03-27  3:40   ` Wu, Bryan
2007-03-27  3:57     ` Paul Mundt
2007-03-27  4:34       ` Mike Frysinger
2007-03-27  4:49         ` Paul Mundt
2007-03-27  5:17           ` Mike Frysinger
2007-03-27  5:27             ` Randy Dunlap
2007-03-27  5:40               ` Wu, Bryan
2007-03-27  8:27                 ` Sam Ravnborg [this message]
2007-03-27 15:34                 ` Randy Dunlap
2007-03-28  2:06                   ` Wu, Bryan
2007-03-28  2:13                     ` Randy Dunlap
2007-03-27  5:32             ` Wu, Bryan

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=20070327082722.GC2031@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bryan.wu@analog.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox