linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Linux F2FS DEV,
	Mailing List" <linux-f2fs-devel@lists.sourceforge.net>,
	"Linux Kernel, Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux FS DEV, Mailing List" <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] f2fs fixes for v3.8-rc7
Date: Fri, 08 Feb 2013 13:20:31 +0900	[thread overview]
Message-ID: <1360297231.8037.8.camel@kjgkr> (raw)
In-Reply-To: <20130208031021.GF4503@ZenIV.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

2013-02-08 (금), 03:10 +0000, Al Viro:
> On Fri, Feb 08, 2013 at 12:09:34PM +1100, Linus Torvalds wrote:
> > No.
> > 
> > You guys need to realize that I'm not talking crap like this this late.
> > 
> > This is not major bugfixes. I already looked away once just because
> > it's a new filesystem, but enough is enough. This is way way WAY too
> > late to start sendign "enhancements". Seriously.
> > 
> > Send them for the next merge window. Not just before rc7.
> 
> BTW, for the next merge window I've got several patches to that sucker;
> commits f3d9d7e..10e4e72 in vfs.git.  I can send them to f2fs tree or
> have them go in vfs one, but this stuff needs to be dealt with.  Fake
> struct dentry on stack is a bad thing with capital Hell No...

Hi Al,

Could you send the patches to me?
I'll merge them in my tree and submit them in the next merge window.
Is it OK?

Thanks,

-- 
Jaegeuk Kim
Samsung

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-02-08  4:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07  0:21 [GIT PULL] f2fs fixes for v3.8-rc7 Jaegeuk Kim
2013-02-08  1:09 ` Linus Torvalds
2013-02-08  3:10   ` Al Viro
2013-02-08  4:20     ` Jaegeuk Kim [this message]
2013-02-08  8:01       ` Al Viro
2013-02-08 10:54         ` Stephen Rothwell
2013-02-08  4:16   ` Jaegeuk Kim

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=1360297231.8037.8.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).