From: Andreas Dilger <adilger@clusterfs.com>
To: Jacky Lam <snakie@ismart.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel patches
Date: Fri, 8 Mar 2002 10:42:28 -0700 [thread overview]
Message-ID: <20020308174228.GD24615@turbolinux.com> (raw)
In-Reply-To: <00ea01c1c6c6$083faea0$eb4a0a3d@homeuc1hfbdu7w>
In-Reply-To: <00ea01c1c6c6$083faea0$eb4a0a3d@homeuc1hfbdu7w>
On Mar 09, 2002 01:23 +0800, Jacky Lam wrote:
> I want to make some statistics on all kernel patches. Could someone tell
> me how can I gather all the patches sending to Linus, Alan Cox.....?
Search mail archives for the subject [PATCH]. Note that it would be
very difficult to correlate _submitted_ patches with _accepted_ patches,
unless you had some smarts to detect that a later kernel had that patch
applied. That is complicated by the fact that submitted and applied
patches are not always exactly the same.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2002-03-08 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 17:23 Kernel patches Jacky Lam
2002-03-08 17:42 ` Andreas Dilger [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=20020308174228.GD24615@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snakie@ismart.net \
/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