From: Dave Hansen <haveblue@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Matt Mackall <mpm@selenic.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ketchup versus patch-kernel
Date: Fri, 20 Aug 2004 10:47:32 -0700 [thread overview]
Message-ID: <1093024052.15662.1245.camel@nighthawk> (raw)
In-Reply-To: <20040820193835.GB7298@mars.ravnborg.org>
On Fri, 2004-08-20 at 12:38, Sam Ravnborg wrote:
> On Fri, Aug 20, 2004 at 10:06:48AM -0700, Dave Hansen wrote:
> > Since 2.6.8.1 came out, I'm sure a lot of automated tools stopped
> > working, ketchup included.
>
> Can someone please explain to me what is the difference between
> patch-kernel and ketchup?
In my view, there's no basic difference in their intention: turn one
kernel version into another. Although, ketchup does handle a few more
things like downloads, gpg, and a wider variety of trees like -mm, -mjb
and -tiny.
-- Dave
next prev parent reply other threads:[~2004-08-20 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 17:06 [PATCH] ketchup - support new -post releases Dave Hansen
2004-08-20 19:38 ` ketchup versus patch-kernel Sam Ravnborg
2004-08-20 17:47 ` Dave Hansen [this message]
2004-08-21 14:14 ` [PATCH] ketchup - support new -post releases Matt Mackall
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=1093024052.15662.1245.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rddunlap@osdl.org \
--cc=sam@ravnborg.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