From: "Theodore Tso" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL 5/9] fuse2fs: refactor mount code
Date: Thu, 2 Apr 2026 09:55:03 -0400 [thread overview]
Message-ID: <20260402135503.GD15407@macsyma-wired.lan> (raw)
In-Reply-To: <177334916576.3254574.12995451033800002505.stg-ugh@frogsfrogsfrogs>
On Thu, Mar 12, 2026 at 02:00:42PM -0700, Darrick J. Wong wrote:
> Hi Ted,
>
> Please pull this branch with changes for ext4.
>
> As usual, I did a test-merge with the main upstream branch as of a few
> minutes ago, and didn't see any conflicts. Please let me know if you
> encounter any problems.
>
> The following changes since commit 5d3394ff8d6f2e120be1343c1504831d9602a3b4:
>
> fuse2fs: hoist unmount code from main (2026-03-08 19:14:05 -0700)
Thanks, merged into the next branch.
- Ted
next prev parent reply other threads:[~2026-04-02 13:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:57 [PULLBOMB v2 1.48] fuse2fs: new features, new server Darrick J. Wong
2026-03-12 20:59 ` [GIT PULL 1/9] fuse2fs: fix locking problems Darrick J. Wong
2026-03-19 14:44 ` Theodore Tso
2026-03-12 20:59 ` [GIT PULL 2/9] fuse2fs: add some easy new features Darrick J. Wong
2026-03-19 14:59 ` Theodore Tso
2026-03-12 21:00 ` [GIT PULL 3/9] fuse2fs: clean up operation startup Darrick J. Wong
2026-04-02 13:48 ` Theodore Tso
2026-03-12 21:00 ` [GIT PULL 4/9] fuse2fs: refactor unmount code Darrick J. Wong
2026-04-02 13:51 ` Theodore Tso
2026-03-12 21:00 ` [GIT PULL 5/9] fuse2fs: refactor mount code Darrick J. Wong
2026-04-02 13:55 ` Theodore Tso [this message]
2026-03-12 21:00 ` [GIT PULL 6/9] fuse2fs: improve operation tracing Darrick J. Wong
2026-04-02 13:59 ` Theodore Tso
2026-03-12 21:01 ` [GIT PULL 7/9] fuse2fs: better tracking of writable state Darrick J. Wong
2026-04-02 14:00 ` Theodore Tso
2026-03-12 21:01 ` [GIT PULL 8/9] fuse2fs: upgrade to libfuse 3.17 Darrick J. Wong
2026-03-12 21:01 ` [GIT PULL 9/9] fuse4fs: fork a low level fuse server Darrick J. Wong
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=20260402135503.GD15407@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.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.