From: Linus Torvalds <email@example.com> To: Konstantin Komarov <firstname.lastname@example.org>, Stephen Rothwell <email@example.com> Cc: "Leonidas P. Papadakos" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "Darrick J. Wong" <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org>, Hans de Goede <email@example.com>, linux-fsdevel <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, Al Viro <firstname.lastname@example.org>, Matthew Wilcox <email@example.com> Subject: Re: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Date: Thu, 2 Sep 2021 14:55:20 -0700 [thread overview] Message-ID: <CAHk-=wg7GMGD1YNM7WgPAU3nwHhMAvQ8yvdwvJtuwe9J1pBgvg@mail.gmail.com> (raw) In-Reply-To: <CAHk-=wjn4W-7ZbHrw08cWy=12DgheFUKLO5YLgG6in5TA5HxqQ@mail.gmail.com> On Fri, Jul 30, 2021 at 10:23 AM Linus Torvalds <firstname.lastname@example.org> wrote: > > Well, I won't pull until the next merge window opens anyway (about a > month away). But it would be good to have your tree in linux-next for > at least a couple of weeks before that happens. > > Added Stephen to the participants list as a heads-up for him - letting > him know where to fetch the git tree from will allow that to happen if > you haven't done so already. Ok, so I've merged the biggest pieces of this merge window, and I haven't actually seen a NTFSv3 pull request yet. I wonder if you expected that being in linux-next just "automatically" causes the pull to happen, because that's not the case. We often have things "brewing" in linux-next for a while, and it's there for testing but not necessarily ready for prime time. So linux-next is a preparatory thing, not a "this will get merged" So to actually merge things, I will expect to get an explicit pull request with the usual diffstat and shortlog, to show that yes, you really think it's all good, and it's ready to merge. Don't worry about - and don't try to fix - merge conflicts with possible other work that has been going on. Stephen fixes it for linux-next and makes people aware of it, and I want to _know_ about them, but I will then handle and re-do the merge conflicts myself based on what I have actually merged up to that point. And of course, the other side of that is that if linux-next uncovered other issues, or if there are things holding things up, please _don't_ feel obligated to send me a pull request. There is always the next merge window. Linus
next prev parent reply other threads:[~2021-09-02 21:56 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-13 10:45 [GIT PULL] vboxsf fixes for 5.14-1 Hans de Goede 2021-07-13 19:15 ` Linus Torvalds 2021-07-13 20:14 ` Al Viro 2021-07-13 20:18 ` Al Viro 2021-07-13 20:24 ` Randy Dunlap 2021-07-13 20:32 ` Al Viro 2021-07-13 21:43 ` Randy Dunlap 2021-07-14 10:50 ` Rafał Miłecki 2021-07-14 14:13 ` Christoph Hellwig 2021-07-14 14:51 ` Greg KH 2021-07-14 15:59 ` Rafał Miłecki 2021-07-14 16:05 ` Matthew Wilcox 2021-07-14 16:18 ` Rafał Miłecki 2021-07-15 21:50 ` Neal Gompa 2021-07-16 11:46 ` Leonidas P. Papadakos 2021-07-16 18:07 ` Linus Torvalds 2021-07-30 15:55 ` Konstantin Komarov 2021-07-30 17:23 ` Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Linus Torvalds 2021-08-13 16:11 ` Konstantin Komarov 2021-08-15 20:32 ` Stephen Rothwell 2021-08-16 3:00 ` Kari Argillander 2021-09-02 21:55 ` Linus Torvalds [this message] 2021-08-03 22:48 ` [GIT PULL] vboxsf fixes for 5.14-1 Theodore Ts'o 2021-08-03 23:44 ` Matthew Wilcox 2021-08-04 0:04 ` Theodore Ts'o 2021-08-04 0:10 ` Linus Torvalds 2021-08-04 0:49 ` Theodore Ts'o 2021-08-04 1:03 ` Darrick J. Wong 2021-08-04 6:38 ` Kari Argillander 2021-08-04 16:30 ` Theodore Ts'o 2021-08-05 15:48 ` Konstantin Komarov 2021-08-10 7:02 ` Darrick J. Wong 2021-09-02 22:09 ` NTFS testing (was: " Szabolcs Szakacsits 2021-09-03 17:48 ` Eric Biggers 2021-09-03 21:17 ` Szabolcs Szakacsits 2021-07-17 16:47 ` Pali Rohár 2021-07-14 16:13 ` Darrick J. Wong 2021-07-14 16:18 ` Christoph Hellwig 2021-07-14 16:38 ` Gao Xiang 2021-07-14 20:03 ` Eric W. Biederman 2021-07-15 22:14 ` Darrick J. Wong 2021-07-13 19:17 ` 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='CAHk-=wg7GMGD1YNM7WgPAU3nwHhMAvQ8yvdwvJtuwe9J1pBgvg@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)' \ /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
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).