From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [GIT PULL] f2fs for 5.6-rc6
Date: Wed, 11 Mar 2020 10:48:37 -0700 [thread overview]
Message-ID: <20200311174837.GA82207@google.com> (raw)
In-Reply-To: <CAHk-=wiVpnOo9MyOpHxAyuv0ZBGCsW2tMmOtwb+6CX-taKRtKQ@mail.gmail.com>
On 03/11, Linus Torvalds wrote:
> On Wed, Mar 11, 2020 at 10:35 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > I actually merged the last three patches which were introduced yesterday.
> >
> > Others were merged over a week ago.
>
> No, three were done just before you sent the pull request, and then
> seven others were done yesterday.
Due to my rebase work. :(
>
> Yes, the rest were a week ago.
>
> But basically, by rc6, I want to get the warm and fuzzies that the
> code has been tested, seen review, and isn't some last-minute
> addition.
Ok, I see. Let me prepare them for next merge window.
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL] f2fs for 5.6-rc6
Date: Wed, 11 Mar 2020 10:48:37 -0700 [thread overview]
Message-ID: <20200311174837.GA82207@google.com> (raw)
In-Reply-To: <CAHk-=wiVpnOo9MyOpHxAyuv0ZBGCsW2tMmOtwb+6CX-taKRtKQ@mail.gmail.com>
On 03/11, Linus Torvalds wrote:
> On Wed, Mar 11, 2020 at 10:35 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > I actually merged the last three patches which were introduced yesterday.
> >
> > Others were merged over a week ago.
>
> No, three were done just before you sent the pull request, and then
> seven others were done yesterday.
Due to my rebase work. :(
>
> Yes, the rest were a week ago.
>
> But basically, by rc6, I want to get the warm and fuzzies that the
> code has been tested, seen review, and isn't some last-minute
> addition.
Ok, I see. Let me prepare them for next merge window.
Thanks,
next prev parent reply other threads:[~2020-03-11 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 16:27 [GIT PULL] f2fs for 5.6-rc6 Jaegeuk Kim
2020-03-11 17:20 ` [f2fs-dev] " Linus Torvalds
2020-03-11 17:20 ` Linus Torvalds
2020-03-11 17:35 ` [f2fs-dev] " Jaegeuk Kim
2020-03-11 17:35 ` Jaegeuk Kim
2020-03-11 17:41 ` [f2fs-dev] " Linus Torvalds
2020-03-11 17:41 ` Linus Torvalds
2020-03-11 17:48 ` Jaegeuk Kim [this message]
2020-03-11 17:48 ` Jaegeuk Kim
2020-04-07 21:05 ` [f2fs-dev] " pr-tracker-bot
2020-04-07 21:05 ` pr-tracker-bot
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=20200311174837.GA82207@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.