mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] CFS scheduler, -v10
Date: Mon, 07 May 2007 14:35:42 -0400	[thread overview]
Message-ID: <m3abwgqy5m.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20070507163342.GA3502@elte.hu> (Ingo Molnar's message of "Mon\, 7 May 2007 18\:33\:42 +0200")

I finally had time to try bisecting the problem I was having with cfs8
and master Sunday, and was able to eliminate the problem.

I had first done:

  clone
  branch
  checkout
  apply
  commit
  pull

If instead of pulling master into the cfs branch, I rather switch to the
master branch and pull the cfs branch into that, it works.

I'll try updating to the current master with v10 to confirm.

For those who want to follow, do:


#!/bin/sh
git clone -l -s -n \
 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git \
 2.6.21-cfs-master
cd 2.6.21-cfs-master
git checkout -b git checkout -b cfs v2.6.21
git pull git://people.freedesktop.org/~cloos/cfs-2.6.git
git checkout master
git pull . cfs


The master branch of git://people.freedesktop.org/~cloos/cfs-2.6.git
has 2.6.21 with the sched-cfs-v10-v2.6.21.1.patch.  Cf gitweb at:

http://gitweb.freedesktop.org/?p=/users/cloos/cfs-2.6.git

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

  reply	other threads:[~2007-05-07 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 16:33 Ingo Molnar
2007-05-07 18:35 ` James Cloos [this message]
2007-05-07 18:40   ` Ingo Molnar
2007-05-07 19:32     ` James Cloos
2007-05-07 18:49   ` James Cloos
2007-05-07 20:43 ` Paolo Ciarrocchi
2007-05-08  0:47 ` Fortier,Vincent [Montreal]
2007-05-08  7:51 ` Mike Galbraith
2007-05-08  8:32   ` Mike Galbraith
2007-05-09 11:21 Al Boldi

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=m3abwgqy5m.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®