From: Randy Dunlap <rdunlap@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.9-rc1
Date: Sun, 03 Mar 2013 18:32:12 -0800 [thread overview]
Message-ID: <513407AC.8060009@infradead.org> (raw)
In-Reply-To: <CA+55aFxA1pH_aKJc85DXuS2-Q=7b4pP-h_ms6XQiSzQcpWaO6Q@mail.gmail.com>
On 03/03/13 17:42, Linus Torvalds wrote:
> On Sun, Mar 3, 2013 at 5:17 PM, Jiri Kosina <jkosina@suse.cz> wrote:
>>
>> I actually quite liked your merge shortlog, which of course I can generate
>> easily myself, but it was nice to have for free :)
>
> No, you're right, I should do it. In fact, I should automate it better
> so that I do it by default and don't have to do so much hand-editing
> of the result of a (really) stupid shell script.
>
> It's all based on just
>
> git log v3.8.. --author=Torvalds --merges |
> egrep '^ ((Merge)|(Pull)) .* from '
>
> and then some nasty sed+sort crud, followed by some manual fixup. It's
> the kind of thing perl is perfect for, but I'm not much of a perl
> person, so I have never written a *good* script to just do this right.
>
> Anyway, here it is, the merge-log of stuff that happened in the merge
> window for 3.9.
>
> Linus
>
> ---
I suppose that this omits individual contributor patches by design?
I had 3 patches merged, but they are hidden by this method.
> James Bottomley:
> first round of SCSI updates
> SCSI updates
1 here
> Wim Van Sebroeck:
> watchdog updates
1 here
and 1 merged by Linus Torvalds.
thanks,
--
~Randy
next prev parent reply other threads:[~2013-03-04 2:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 0:28 Linux 3.9-rc1 Linus Torvalds
2013-03-04 1:17 ` Jiri Kosina
2013-03-04 1:42 ` Linus Torvalds
2013-03-04 2:32 ` Randy Dunlap [this message]
2013-03-04 2:55 ` Linus Torvalds
2013-03-04 3:39 ` Linus Torvalds
2013-03-04 4:22 ` linux-next stats (Was: Linux 3.9-rc1) Stephen Rothwell
2013-03-04 5:02 ` Stephen Rothwell
2013-03-04 9:54 ` Regression from 3.8.0 - USB mouse (was: " Harald Arnesen
2013-03-06 8:06 ` Linux 3.9-rc1 Henrik Rydberg
2013-03-06 9:17 ` H. Peter Anvin
2013-03-06 10:07 ` Henrik Rydberg
2013-03-06 17:51 ` Yinghai Lu
2013-03-06 19:36 ` Henrik Rydberg
2013-03-06 19:34 ` H. Peter Anvin
2013-03-06 19:54 ` Henrik Rydberg
2013-03-06 20:00 ` Yinghai Lu
2013-03-06 20:45 ` Henrik Rydberg
2013-03-06 20:58 ` H. Peter Anvin
2013-03-06 21:33 ` Yinghai Lu
2013-03-06 21:49 ` H. Peter Anvin
2013-03-06 22:04 ` Henrik Rydberg
2013-03-06 22:27 ` H. Peter Anvin
2013-03-06 22:44 ` Yinghai Lu
2013-03-06 22:48 ` H. Peter Anvin
2013-03-06 22:54 ` Yinghai Lu
2013-03-07 4:28 ` [tip:x86/urgent] x86, mm: Make sure to find a 2M free block for the first mapped area tip-bot for Yinghai Lu
2013-03-06 22:14 ` Linux 3.9-rc1 Yinghai Lu
2013-03-06 22:19 ` Yinghai Lu
2013-03-06 22:28 ` H. Peter Anvin
2013-03-06 22:46 ` Yinghai Lu
2013-03-06 22:47 ` H. Peter Anvin
2013-03-06 16:08 ` Linus Torvalds
2013-03-06 16:57 ` H. Peter Anvin
2013-03-06 21:07 ` Henrik Rydberg
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=513407AC.8060009@infradead.org \
--to=rdunlap@infradead.org \
--cc=jkosina@suse.cz \
--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