linux-kernel - Re: [GIT PULL] f2fs fixes for v4.6-rc3

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]

Date:	Mon, 4 Apr 2016 13:07:11 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jaegeuk Kim <jaegeuk@...nel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux FS Dev Mailing List <linux-fsdevel@...r.kernel.org>,
	Linux F2FS Dev Mailing List 
	<linux-f2fs-devel@...ts.sourceforge.net>
Subject: Re: [GIT PULL] f2fs fixes for v4.6-rc3

On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim <jaegeuk@...nel.org> wrote:
>
> Could you please pull the below commits for v4.6-rc3?

Pulled, but..

>   git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-linus

.. the above is a tag, but it's not signed, nor even annotated. So it
has no message about what the fixes are in it, it's just the plain
SHA1 id.

Now, I don't really require signed tags from kernel.org, but it would
still be nice. And I *do* want a little blurb about the fixes, even if
it doesn't have to be all that exhaustive. Putting that in the tag is
convenient, but I'm ok with it being just in the email message too,
like you usually do.

This case had neither, so now my merge message is not as descriptive
as I prefer them ;(

             Linus