lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091116210941.GA2622@ldl.fc.hp.com>
Date:	Mon, 16 Nov 2009 14:09:41 -0700
From:	Alex Chiang <achiang@...com>
To:	akpm@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: mmotm 2009-11-13-19-59 uploaded

Hi Andrew,

* akpm@...ux-foundation.org <akpm@...ux-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@...ux-foundation.org>
	Date:   Mon Nov 9 20:59:36 2009 +0100

	    fed up with those stupid warnings
	    
	    
	    Signed-off-by: Andrew Morton <akpm@...ux-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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ