From: aq <aquynh@gmail.com>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: David Lang <david.lang@digitalinsight.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.12
Date: Sun, 19 Jun 2005 10:00:05 -0500 [thread overview]
Message-ID: <9cde8bff0506190800170a3685@mail.gmail.com> (raw)
In-Reply-To: <20050618193636.70ab8b05.rdunlap@xenotime.net>
On 6/18/05, randy_dunlap <rdunlap@xenotime.net> wrote:
> On Sat, 18 Jun 2005 18:48:59 -0700 (PDT) David Lang wrote:
>
> | On Sat, 18 Jun 2005, aq wrote:
> |
> | > the version number is a little bit confused here: if I want to upgrade
> | > from for example 2.6.11.5 to 2.6.12, which patch should I get?
> |
> | you reverse the 2.6.11 -> 2.6.11.5 patch to get back to a vinilla 2.6.11
> | then you apply the 2.6.11->2.6.12 patch.
>
> Hrm, I expected ketchup to be able to handle that already.
> Does it not?
ah yes. because 2.6.12 can be get by patching from 2.6.11, so ketchup
works well, as always.
but ketchup doesnt work with 2.6.x.y yet.
regards,
aq
next prev parent reply other threads:[~2005-06-19 15:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 19:05 Linux 2.6.12 Nick Warne
2005-06-18 19:20 ` Jim Crilly
2005-06-18 19:33 ` Jesper Juhl
2005-06-19 1:39 ` aq
2005-06-19 1:48 ` David Lang
2005-06-19 2:36 ` randy_dunlap
2005-06-19 9:29 ` Ian Campbell
2005-06-19 15:00 ` aq [this message]
2005-06-20 9:36 ` Vincent Hanquez
2005-06-20 21:55 ` Matt Mackall
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 5:13 Linus Torvalds
2005-06-18 5:38 ` Keith Owens
2005-06-18 6:05 ` Linus Torvalds
2005-06-18 6:59 ` Willy Tarreau
2005-06-18 10:36 ` Jesper Juhl
2005-06-18 10:48 ` Alexey Dobriyan
2005-06-18 10:52 ` Jesper Juhl
2005-06-18 10:54 ` Brice Goglin
2005-06-18 17:42 ` Linus Torvalds
2005-06-18 18:26 ` Steven Rostedt
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=9cde8bff0506190800170a3685@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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