From: Avi Kivity <avi@qumranet.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [-mmotm] some different buliding failures
Date: Wed, 02 Jul 2008 17:00:01 +0300 [thread overview]
Message-ID: <486B89E1.7060800@qumranet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807021312220.23201@blonde.site>
Hugh Dickins wrote:
> On Wed, 2 Jul 2008, Avi Kivity wrote:
>
>> I'm sure you have before, but can you remind me how to figure out what commit
>> to apply mmotm onto? I looked in series and origin.patch, but no luck.
>> Applying on top of the last (first) commit in origin.patch's head did not
>> work.
>>
>
> I look at its mm.patch, which today shows
>
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 26
> -EXTRAVERSION = -rc8
> +EXTRAVERSION = -rc8-mm1
>
> which hints that it applies to a 2.6.26-rc8 tree.
>
>
Thanks. That worked.
>> Also, can I suggest including series in b-o.tar.gz?
>> Nice to have everything in one tarball.
>>
>
> It is included, but (I can't tell you why) one level up.
> You should find these three in the directory you extracted
> into, I promptly move them down into broken-out itself.
>
> .DATE
> .DATE=2008-07-02-04-02
> series
>
> Hugh (probably _not_ extracted into your current directory ;)
>
Thanks 2.
Anyway I've fixed the warnings and will push out the fix shortly.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-07-02 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 6:23 [-mmotm] some different buliding failures Li Zefan
2008-07-02 8:02 ` Andrew Morton
2008-07-02 8:20 ` Paul Mundt
2008-07-02 8:29 ` Ben Dooks
2008-07-02 8:14 ` Andrew Morton
2008-07-02 8:18 ` Li Zefan
2008-07-02 11:01 ` Andrew Morton
2008-07-02 11:48 ` Avi Kivity
2008-07-02 12:23 ` Hugh Dickins
2008-07-02 14:00 ` Avi Kivity [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=486B89E1.7060800@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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