From: Thorsten Leemhuis <fedora@leemhuis•info>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: Tree for June 22
Date: Mon, 22 Jun 2009 19:23:31 +0200 [thread overview]
Message-ID: <4A3FBE13.9050201@leemhuis.info> (raw)
In-Reply-To: <20090622182600.129da88e.sfr@canb.auug.org.au>
/me drops LKML from CC, as this is linux-next specific
Hi!
Just a quick question from a git rookie:
On 22.06.2009 10:26, Stephen Rothwell wrote:
> On Mon, 22 Jun 2009 18:19:20 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>> Changes since 20090619:
>
> The current "git diff --stat -M stable..HEAD^" ends like this:
Side note: above command doesn't work here (Fedora 11, git version 1.6.2.2):
$ git diff --stat -M 'stable..HEAD^'
fatal: ambiguous argument 'stable..HEAD^': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions
This command OTOH...
$ git diff --stat -M 'origin/stable..origin/HEAD^'
...seems to work just fine and gives the result your posted:
> 835 files changed, 46602 insertions(+), 14044 deletions(-)
I just mention it because it might be relevant. The real reason why I
write this mail is this:
Is it possible somehow to export the individual patches that are
currently in linux-next? I tried
git format-patch -M -o ../tmp 'origin/stable..origin/HEAD^'
but that resulted in 3269 files with commits/patches that sum up to
38 MByte. Some of those patches (seems 1919 alone from the KVM tree...)
are quite old. The first one for example is
0001-KVM-mmu-add-missing-dirty-page-tracking-cases.patch :
"""
> From 2959cd13ecc1fbe1b2339937481844ff963f1e7f Mon Sep 17 00:00:00 2001
> From: Avi Kivity <avi@qumranet•com>
> Date: Mon, 19 Feb 2007 14:37:46 +0200
> Subject: [PATCH 0001/3269] KVM: mmu: add missing dirty page tracking cases
>
> We fail to mark a page dirty in three cases:
>
> - setting the accessed bit in a pte
> - setting the dirty bit in a pte
> - emulating a write into a pagetable
>
> This fix adds the missing cases.
> [...]
"""
It afaics was merged in linus tree ages ago:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bf3f8e86c2e22b9bd1375be1bbbd67384dba4342
I suspect I do something wrong, but I could not find what exactly what
I'm doing wrong... Could anybody give me some insight/help? tia!
CU
knurd
next prev parent reply other threads:[~2009-06-22 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 8:19 linux-next: Tree for June 22 Stephen Rothwell
2009-06-22 8:26 ` Stephen Rothwell
2009-06-22 17:23 ` Thorsten Leemhuis [this message]
2009-06-23 1:48 ` Stephen Rothwell
2009-06-22 15:51 ` [PATCH -next] hwlat: depends on RING_BUFFER (build fix) Randy Dunlap
2009-06-22 21:14 ` Jon Masters
2009-06-22 16:19 ` linux-next: Tree for June 22 (x86/kvm) Randy Dunlap
2009-06-25 4:01 ` Stephen Rothwell
2009-06-25 11:50 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2010-06-22 6:05 linux-next: Tree for June 22 Stephen Rothwell
2010-06-22 7:53 ` Geert Uytterhoeven
2010-06-22 10:22 ` Stephen Rothwell
2011-06-22 6:36 Stephen Rothwell
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=4A3FBE13.9050201@leemhuis.info \
--to=fedora@leemhuis$(echo .)info \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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