From: Linus Torvalds <firstname.lastname@example.org>
To: Konstantin Komarov <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Subject: Re: [GIT PULL] ntfs3: bugfixes for 6.0
Date: Wed, 17 Aug 2022 14:55:38 -0700 [thread overview]
Message-ID: <CAHk-=wg53xW_ppC5w_tDvWKn3Q7i-hWmd09KM-O1npQHWoBBGw@mail.gmail.com> (raw)
On Wed, Aug 17, 2022 at 9:43 AM Konstantin Komarov
> Please pull this branch containing ntfs3 code for 6.0.
This really should have come in during the merge window.
Yes, there are clearly several fixes in here, but at least that
FALLOC_FL_INSERT_RANGE is clearly new development. And a lot of it
looks like just refactoring and cleanup, and again that is something
that should come in during the merge window.
But since this all affects only ntfs3, and I consider that still
fairly solidly experimental, I'll let it slide. But please keep this
in mind for next time - new work (whether cleanups or actual new code)
during the merge window, and obvious fixes afterwards.
next prev parent reply other threads:[~2022-08-17 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 16:43 [GIT PULL] ntfs3: bugfixes for 6.0 Konstantin Komarov
2022-08-17 21:55 ` Linus Torvalds [this message]
2022-08-17 22:20 ` pr-tracker-bot
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).