From: David Sterba <dsterba@suse.cz>
To: Sun YangKai <sunk67188@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Remaining BTRFS_PATH_AUTO_FREE work
Date: Thu, 21 Aug 2025 14:36:27 +0200 [thread overview]
Message-ID: <20250821123627.GS22430@suse.cz> (raw)
In-Reply-To: <6181995.lOV4Wx5bFT@saltykitkat>
On Tue, Aug 19, 2025 at 10:03:45AM +0800, Sun YangKai wrote:
> There's no such pattern in files beginning with p, and files beginning with z
> has been converted. So files beginning with [r-x] need this work. I'm doing
> this on files beginning with r.
>
> BTW, should we also do this for files in the test dir?
Yes, thanks.
next prev parent reply other threads:[~2025-08-21 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 2:03 Remaining BTRFS_PATH_AUTO_FREE work Sun YangKai
2025-08-19 3:13 ` Sun YangKai
2025-08-21 12:36 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 17:10 David Sterba
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=20250821123627.GS22430@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sunk67188@gmail.com \
/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