From: "Theodore Tso" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL 2/9] fuse2fs: add some easy new features
Date: Thu, 19 Mar 2026 10:59:46 -0400 [thread overview]
Message-ID: <20260319145946.GB14752@macsyma-wired.lan> (raw)
In-Reply-To: <177334916488.3254574.394222234133985617.stg-ugh@frogsfrogsfrogs>
On Thu, Mar 12, 2026 at 01:59:55PM -0700, Darrick J. Wong wrote:
> Please pull this branch with changes for ext4.
When reviewing this patch series, I noticed that the
debian/libext2fs2t64.symbols file used the version number of 1.47.4
for the new symbols. I'll fix it up after doing the pull, but in the
future, it's probably simpler if you don't try to adjust the debian
symbol files. I generally will take care of that before I do a Debian
release.
Thanks,
- Ted
next prev parent reply other threads:[~2026-03-19 15:00 UTC|newest]
Thread overview: 12+ 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 [this message]
2026-03-12 21:00 ` [GIT PULL 3/9] fuse2fs: clean up operation startup Darrick J. Wong
2026-03-12 21:00 ` [GIT PULL 4/9] fuse2fs: refactor unmount code Darrick J. Wong
2026-03-12 21:00 ` [GIT PULL 5/9] fuse2fs: refactor mount code Darrick J. Wong
2026-03-12 21:00 ` [GIT PULL 6/9] fuse2fs: improve operation tracing Darrick J. Wong
2026-03-12 21:01 ` [GIT PULL 7/9] fuse2fs: better tracking of writable state Darrick J. Wong
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=20260319145946.GB14752@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox