From: Con Kolivas <kernel@kolivas.org>
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Cc: ck kernel mailing list <ck@vds.kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-ck6
Date: Fri, 30 Jul 2004 15:22:27 +1000 [thread overview]
Message-ID: <4109DB13.4000705@kolivas.org> (raw)
In-Reply-To: <4109D85A.3030003@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
Prakash K. Cheemplavam wrote:
> Con Kolivas wrote:
> | Patchset update:
>
> Hi, what happened to the incremental updates, ie ck5->ck6? I don't want
> to reverse ck5 and then apply ck6, as my kernel is furthermore patched
> and this complicates stuff...
Here:
http://ck.kolivas.org/patches/2.6/2.6.7/from_2.6.7-ck5_to_2.6.7-ck6.bz2
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-07-30 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 1:49 2.6.7-ck6 Con Kolivas
2004-07-30 5:10 ` 2.6.7-ck6 Prakash K. Cheemplavam
2004-07-30 5:22 ` Con Kolivas [this message]
2004-07-30 5:38 ` 2.6.7-ck6 Prakash K. Cheemplavam
2004-07-30 7:03 ` [ck] 2.6.7-ck6 Daniel Caujolle-Bert
2004-07-30 10:32 ` Con Kolivas
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=4109DB13.4000705@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakashkc@gmx.de \
/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