From: Alex Chiang <achiang@hp.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmotm 2009-11-13-19-59 uploaded
Date: Mon, 16 Nov 2009 14:09:41 -0700 [thread overview]
Message-ID: <20091116210941.GA2622@ldl.fc.hp.com> (raw)
In-Reply-To: <200911140403.nAE43CN1016851@imap1.linux-foundation.org>
Hi Andrew,
* akpm@linux-foundation.org <akpm@linux-foundation.org>:
> The mm-of-the-moment snapshot 2009-11-13-19-59 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> and will soon be available at
>
> git://zen-kernel.org/kernel/mmotm.git
>
> It contains the following patches against 2.6.32-rc7:
Many of the patches have dropped their subject lines. I realize
that you can get the subject of the patch from the patch name,
but if one is using the git tree, then looking at the git log,
you see things like:
commit 7f97d096be78d5a8d6bf2efc28fe3efba21e47f0
Author: Andrew Morton <akpm@linux-foundation.org>
Date: Mon Nov 9 20:59:36 2009 +0100
fed up with those stupid warnings
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
And there's no real good way to know that it came from
undeprecate-pci_find_device.patch.
Would it be reasonable of me to request that your scripts stick
the subject of the mail into the patch description field? That
would greatly enhance the useability of the git version of mmotm.
Thanks,
/ac
next prev parent reply other threads:[~2009-11-16 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 4:03 mmotm 2009-11-13-19-59 uploaded akpm
2009-11-14 13:28 ` resume crashes in intel_init_thermal [was: mmotm 2009-11-13-19-59 uploaded] Jiri Slaby
2009-11-14 16:15 ` Andrew Morton
2009-11-14 18:44 ` Jiri Slaby
2009-11-15 8:07 ` Ingo Molnar
2009-11-16 21:09 ` Alex Chiang [this message]
2009-11-16 21:36 ` mmotm 2009-11-13-19-59 uploaded Andrew Morton
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=20091116210941.GA2622@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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