From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.136]:49550 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751774AbcDDVPG (ORCPT ); Mon, 4 Apr 2016 17:15:06 -0400 Date: Mon, 4 Apr 2016 14:15:02 -0700 From: Jaegeuk Kim To: Linus Torvalds Cc: Linux Kernel Mailing List , Linux FS Dev Mailing List , Linux F2FS Dev Mailing List Subject: Re: [GIT PULL] f2fs fixes for v4.6-rc3 Message-ID: <20160404211502.GA84643@jaegeuk> References: <20160404052110.GB80122@jaegeuk.ucsc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Apr 04, 2016 at 01:07:11PM -0700, Linus Torvalds wrote: > On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim 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. Definitely, will do. Thank you for pulling the patches. Thanks, > > This case had neither, so now my merge message is not as descriptive > as I prefer them ;( > > Linus