From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 21
Date: Sat, 24 Sep 2016 09:28:00 +0200 [thread overview]
Message-ID: <20160924072800.GC4462@kroah.com> (raw)
In-Reply-To: <20160924104245.0d6429c1@canb.auug.org.au>
On Sat, Sep 24, 2016 at 10:42:45AM +1000, Stephen Rothwell wrote:
> Hi Linus,
>
> On Fri, 23 Sep 2016 11:24:04 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > On Tue, Sep 20, 2016 at 11:08 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Changes since 20160920:
> > > [...]
> > > Non-merge commits (relative to Linus' tree): 11180
> > > 8424 files changed, 456474 insertions(+), 237951 deletions(-)
> >
> > What happened here? The previous linux-next tree was much smaller. The
> > "changes since" part doesn't actually talk about the almost 3000 new
> > non-merge commits that very suddenly showed up.
>
> That was Greg's (cc'd) greybus stuff entering the staging tree:
>
> $ git rev-list --count --no-merges origin/master..2bbadafbe4ea
> 2363
This is a staging driver (new hardware bus and drivers), self-contained,
and the development history of the code was preserved by importing it
this way.
The overall size of the kernel only grew by 35k of lines or so, not
much, but yes, the history did jump all at once. Much like when we
imported btrfs the same way.
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-24 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 6:08 linux-next: Tree for Sep 21 Stephen Rothwell
2016-09-23 18:24 ` Linus Torvalds
2016-09-24 0:42 ` Stephen Rothwell
2016-09-24 7:28 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 2:48 Stephen Rothwell
2023-09-21 3:53 ` Stephen Rothwell
2022-09-21 8:57 Stephen Rothwell
2022-09-21 13:13 ` Stephen Rothwell
2022-09-21 15:37 ` Mark Brown
2022-09-21 23:08 ` Stephen Rothwell
2021-09-21 5:52 Stephen Rothwell
2020-09-21 9:24 Stephen Rothwell
2018-09-21 6:09 Stephen Rothwell
2017-09-21 4:04 Stephen Rothwell
2015-09-21 6:05 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=20160924072800.GC4462@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox