linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <dhillf@gmail.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.7-ck1, BFS 426 for linux-3.7
Date: Sun, 16 Dec 2012 18:33:14 +0800	[thread overview]
Message-ID: <CAJd=RBBo2hXsqgz=TbV7CBKsL_W1BNxAESA4OKPqRtQzyiL=uA@mail.gmail.com> (raw)
In-Reply-To: <1911613.U2Pnzoqhvo@hex>

On Sun, Dec 16, 2012 at 5:54 PM, Con Kolivas <kernel@kolivas.org> wrote:
> On Sun, 16 Dec 2012 11:16:31 Con Kolivas wrote:
>> These are patches designed to improve system responsiveness and
>> interactivity with specific emphasis on the desktop, but suitable to
>> any commodity hardware workload.
>>
>> Apply to 3.7.x:
>> -ck-ckhttp://ck.kolivas.org/patches/3.0/3.7/3.71/patch-3.71.bz2
>> or
>> -ck-ckhttp://ck.kolivas.org/patches/3.0/3.7/3.71/patch-3.71.lrz
>>
>> Broken out tarball:
>> -ck-ckhttp://ck.kolivas.org/patches/3.0/3.7/3.71/3.71-broken-out.tar.bz2
>> or
>> -ck-ckhttp://ck.kolivas.org/patches/3.0/3.7/3.71/3.71-broken-out.tar.lrz
>>
>> Discrete patches:
>> -ckhttp://ck.kolivas.org/patches/3.0/3.7/3.71/patches/
>>
>> Latest BFS by itself:
>> http://ck.kolivas.org/patches/bfs/3.0/3.7/3.7-sched-bfs-426.patch
>>
>> Web:
>> http://kernel.kolivas.org
>>
>> Code blog when I feel like it:
>> http://ck-hack.blogspot.com/
>
> Of course these links all got scrambled somehow, but I'm sure you can figure
> out where the patches are :p

Better if changes after 425 are directly attached?

Hillf

  reply	other threads:[~2012-12-16 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16  0:16 [ANNOUNCE] 3.7-ck1, BFS 426 for linux-3.7 Con Kolivas
2012-12-16  9:54 ` Con Kolivas
2012-12-16 10:33   ` Hillf Danton [this message]
2012-12-16 10:34     ` Con Kolivas
2012-12-17 11:16 ` David Rientjes

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='CAJd=RBBo2hXsqgz=TbV7CBKsL_W1BNxAESA4OKPqRtQzyiL=uA@mail.gmail.com' \
    --to=dhillf@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).