public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: bryan.wu@analog.com
Cc: 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 19:13:30 -0700	[thread overview]
Message-ID: <4609CF4A.1030809@oracle.com> (raw)
In-Reply-To: <1175047573.15391.2.camel@roc-desktop>


>>>> In that case, Bryan may like to know that git, mercurial (IIRC),
>>>> and quilt have patchbomb tools.  Also GregKH has one somewhere (he
>>>> can tell you where).  And Paul Jacksone has one at
>>>>   http://www.speakeasy.org/~pj99/sgi/sendpatchset

> 
> Thanks a lot, I will try on my side. And one more question:
> 
> What is patchbomb tools, you mean git, quilt or other kernel patch
> management tool? I am using quilt and try to use git to manage patches.
> Is there a tool just named patchbomb?

No, just the scripts listed above, including quilt & git (except that I can't
find GregKH's script).

-- 
~Randy

PS:  I typo-ed Paul Jackson's name above.  :(

  reply	other threads:[~2007-03-28  2:14 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
2007-03-27 15:34                 ` Randy Dunlap
2007-03-28  2:06                   ` Wu, Bryan
2007-03-28  2:13                     ` Randy Dunlap [this message]
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=4609CF4A.1030809@oracle.com \
    --to=randy.dunlap@oracle.com \
    --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=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