From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL] f2fs fixes for v4.6-rc3
Date: Mon, 4 Apr 2016 14:15:02 -0700 [thread overview]
Message-ID: <20160404211502.GA84643@jaegeuk> (raw)
In-Reply-To: <CA+55aFwa9b5=aYKXNKfCaQN27PFY8GChuhCK+pkrqCfGn6FpKQ@mail.gmail.com>
On Mon, Apr 04, 2016 at 01:07:11PM -0700, Linus Torvalds wrote:
> On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim <jaegeuk@kernel.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.
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
prev parent reply other threads:[~2016-04-04 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 5:21 [GIT PULL] f2fs fixes for v4.6-rc3 Jaegeuk Kim
2016-04-04 20:07 ` Linus Torvalds
2016-04-04 21:15 ` Jaegeuk Kim [this message]
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=20160404211502.GA84643@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).