From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Martin Steigerwald <ms@teamix.de>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CFS scheduler: documentation about scheduling policies
Date: Tue, 23 Sep 2008 14:10:11 +0200 [thread overview]
Message-ID: <1222171811.16700.76.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <200809231401.23432.ms@teamix.de>
On Tue, 2008-09-23 at 14:01 +0200, Martin Steigerwald wrote:
> Am Dienstag, 23. September 2008 schrieb Ingo Molnar:
> > * Martin Steigerwald <ms@teamix.de> wrote:
> > > > please use -p1 to create patches - or since you've just set up the
> > > > tip/master tracking, do something like:
> > >
> > > Okay, lets see how this works out.
> > >
> > > ---
> > > From a57581d4ec3b13f63920b89c336ac9c93c6cf9f0 Mon Sep 17 00:00:00 2001
> > > From: Martin Steigerwald <ms@teamix.de>
> > > Date: Tue, 23 Sep 2008 13:45:46 +0200
> > > Subject: [PATCH] CFS: Documentation about scheduling policies
> >
> > Applied to tip/sched/devel, merged it into tip/master and pushed the
> > result out - thanks Martin.
> >
> > this was a perfect patch :)
>
> Thanks. Now I can learn how I can update my local tip-master ;-). Hmmm, git
> pull seemed to do the trick although it did not touch
> Documentation/scheduler/sched-design-CFS.txt again. Seems it detected that I
> applied the patch I sent you already.
'git remote update' will be best, 'git pull' only works if the
underlying stuff never gets rebased.
prev parent reply other threads:[~2008-09-23 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 9:01 [PATCH] CFS scheduler: documentation about scheduling policies Martin Steigerwald
2008-09-23 9:11 ` Ingo Molnar
2008-09-23 9:53 ` Martin Steigerwald
2008-09-23 10:14 ` Ingo Molnar
2008-09-23 11:48 ` Martin Steigerwald
2008-09-23 11:50 ` Ingo Molnar
2008-09-23 12:01 ` Martin Steigerwald
2008-09-23 12:07 ` Ingo Molnar
2008-09-23 12:10 ` Peter Zijlstra [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=1222171811.16700.76.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ms@teamix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.