From: Matt Mackall <mpm@selenic.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] ketchup - support new -post releases
Date: Sat, 21 Aug 2004 09:14:17 -0500 [thread overview]
Message-ID: <20040821141417.GR31237@waste.org> (raw)
In-Reply-To: <1093021608.15662.1228.camel@nighthawk>
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.
>
> I'm sure this patch isn't complete, but it does work to patch from 2.6.8
> -> 2.6.8.1 or 2.6.8.1-mm*, so it is at least a start.
Unfortunately, we don't yet know how deltas from x.y.z.1 to x.y.z.2
will be handled in the archives, eg relative to x.y.z or incrementally.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2004-08-21 14:14 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
2004-08-21 14:14 ` Matt Mackall [this message]
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=20040821141417.GR31237@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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