linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next stats (Was: Linux 3.12-rc1)
Date: Tue, 17 Sep 2013 09:26:41 +0200	[thread overview]
Message-ID: <CA+icZUWPG2PQx3-c=UeRsad=qbPY=iXyqSGpEhD8RdXdHkHuzQ@mail.gmail.com> (raw)

Hi Stephen,

I am subscribed to linux-next but I did not receive [1].
If you did not CC linux-next, can you do this next time?
Thanks.

Your stats have a lot of number, I am not sure if I read/interpret
them correctly.
Just one number is interesting for me:
How many commits/patches were taken from Linux-next tree 1:1 into v3.12-rc1?
Percentage of them to the total number of commits v3.11..v3.12-rc1?
IOW: How successful is Linux-next?

I am irritated by the number of SHA-IDs vs. number of subject-lines.
If those patches went into v3.12-rc1 from Linux-next both should be
nearly the same.
Can you explain that?

How many trees of maintainers/submaintainers were taken from their
"for-next" trees [2]?
IOW: Without any changes, special preperations "for-linus" (aka
"for-v3.12-rc1")?
IOW #2: How effective work maintainers :-)!

To summarize: I am interested in what went from -next to -rc1 in the
last merge-window.

Thanks for clarification in advance.

Regards,
- Sedat -

P.S.: While digging through the scripts-dir I found "diffconfig". For
your stats I highly recommend to see which Kconfig-options are 1. new
2. changed (name or Y|M|N, especially M->Y).


[1] http://marc.info/?l=linux-kernel&m=137939708327120&w=2
[2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees

                 reply	other threads:[~2013-09-17  7:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CA+icZUWPG2PQx3-c=UeRsad=qbPY=iXyqSGpEhD8RdXdHkHuzQ@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).