From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [GIT PATCH] STAGING merge for .36
Date: Fri, 6 Aug 2010 11:41:49 -0700 [thread overview]
Message-ID: <20100806184149.GA23308@kroah.com> (raw)
In-Reply-To: <AANLkTikzUaTAAu1GqBGqNtvmpfG3z5_HjOCQoVEh9NO9@mail.gmail.com>
On Fri, Aug 06, 2010 at 11:27:02AM -0700, Linus Torvalds wrote:
> On Thu, Aug 5, 2010 at 2:33 PM, Greg KH <greg@kroah.com> wrote:
> > Here's the big staging tree merge for the .36 kernel.
> >
> > 812 files changed, 106306 insertions(+), 33784 deletions(-)
>
> Hmm. How did you generate that diff? It's not what I get. I get
>
> 812 files changed, 107586 insertions(+), 35064 deletions(-)
>
> which is sufficiently different that it makes me worry about what's going on.
Very odd.
I did:
git diff -M --stat --summary origin..HEAD
That's what I've been doing for a while now, and it has been working for
the other trees.
This one was a bit different in that I did have to pull from a different
tree for one of the drivers, but that merged together nicely from what
the end result looked like.
Should I do something else for my pull summaries?
> I pulled it, because the shortlog matched, and it was all in staging
> (except for that one x86 mshyperv line), but I just wonder..
That's good, but I wonder as well.
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-06 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:33 [GIT PATCH] STAGING merge for .36 Greg KH
2010-08-05 22:21 ` [PATCH 288/524] staging: tidspbridge: gen: simplify and clean up Greg Kroah-Hartman
2010-08-06 18:27 ` [GIT PATCH] STAGING merge for .36 Linus Torvalds
2010-08-06 18:41 ` Greg KH [this message]
2010-08-06 23:05 ` Stefan Richter
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=20100806184149.GA23308@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.