public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: "Wu, Bryan" <bryan.wu@analog.com>
Cc: 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 12:57:34 +0900	[thread overview]
Message-ID: <20070327035734.GA25883@linux-sh.org> (raw)
In-Reply-To: <1174966837.6966.13.camel@roc-desktop>

On Tue, Mar 27, 2007 at 11:40:37AM +0800, Wu, Bryan wrote:
> Thanks Arnd. I posted almost ten patches yesterday. Converting ten
> patches to preformatted Emails is terrible manually, you know.
> 
> How does a kernel guru to do this, send out dozens of patch emails a
> day? Is there any convenient tools to help this?
> 
Most people either have patch-bombing scripts or just use git to take
care of it. You should really consider the latter for getting updates
merged in the future, now that most of the initial troubles are resolved.

  reply	other threads:[~2007-03-27  4:00 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 [this message]
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
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=20070327035734.GA25883@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bryan.wu@analog.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox