From: "Tony Luck" <tony.luck@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Short update and pause in 2.6.27 merge window
Date: Fri, 18 Jul 2008 13:46:35 -0700 [thread overview]
Message-ID: <12c511ca0807181346r7aa8f41co26d079d393ddebae@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807170919370.2959@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Thu, Jul 17, 2008 at 9:47 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> We seem to be roughly half-way through the merge window, judging purely by
> number of commits, although part of my calculations there is that I'm
> actually hoping/expecting that because a number of people are on vacation
> etc, this merge window might be smaller than some of the other recent ones
> (2.6.25-rc1 in particular was huge).
That depends on how good people are about putting stuff into linux-next. So far
you've added 3298 non-merge commits in this merge window but the count of
commits in linux-next is less than a thousand below its peak.
We didn't empty linux-next in the last merge, so we probably won't this
time either ... but there are still 4382 commits waiting.
The attached graph of pending work in linux-next was produced with this script
(my linux-next tree has a branch named "linus" which pulls from your tree).
git tag | grep next- | sort | while read tag
do
c=$(git-rev-list --no-merges $tag ^linus | wc -l)
echo ${tag##next-} $c
done
-Tony
[-- Attachment #2: linux-next.png --]
[-- Type: image/png, Size: 3976 bytes --]
prev parent reply other threads:[~2008-07-18 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 16:47 Linus Torvalds
2008-07-18 18:58 ` J. Bruce Fields
2008-07-18 20:46 ` Tony Luck [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=12c511ca0807181346r7aa8f41co26d079d393ddebae@mail.gmail.com \
--to=tony.luck@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome