From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH 0/4] btrfs-progs: fix the filename sanitization of btrfs-image
Date: Fri, 19 Jul 2024 00:55:24 +0200 [thread overview]
Message-ID: <20240718225524.GJ8022@suse.cz> (raw)
In-Reply-To: <87d78bde-b5aa-44bb-926d-a4eabd710c84@gmx.com>
On Fri, Jul 19, 2024 at 08:08:30AM +0930, Qu Wenruo wrote:
> 在 2024/7/19 01:17, David Sterba 写道:
> > On Mon, Jul 15, 2024 at 07:39:32AM +0930, Qu Wenruo wrote:
> >> Ping?
> >>
> >> Any update on this?
> >
> > Tracked as https://github.com/kdave/btrfs-progs/pull/837
>
> Just to mention, since the github review system is working now, do you
> prefer me to still send the updated patches to the ML?
> I'm mostly using the ML as a way to track the work...
You don't need to send it to the mailinglist if there's a PR, for
tracking purposes it's ok to send it. It would be good to keep
dicsussion at one place but I think this won't be common or we'll
manage.
next prev parent reply other threads:[~2024-07-18 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 5:14 [PATCH 0/4] btrfs-progs: fix the filename sanitization of btrfs-image Qu Wenruo
2024-07-08 5:14 ` [PATCH 1/4] btrfs-progs: add warning for -s option " Qu Wenruo
2024-07-08 5:14 ` [PATCH 2/4] btrfs-progs: image: fix the bug that filename sanitization not working Qu Wenruo
2024-07-08 5:14 ` [PATCH 3/4] btrfs-progs: fix rand_range() Qu Wenruo
2024-07-08 5:14 ` [PATCH 4/4] btrfs-progs: misc-tests: add a test case for filename sanitization Qu Wenruo
2024-07-14 22:09 ` [PATCH 0/4] btrfs-progs: fix the filename sanitization of btrfs-image Qu Wenruo
2024-07-18 15:47 ` David Sterba
2024-07-18 22:38 ` Qu Wenruo
2024-07-18 22:55 ` David Sterba [this message]
2024-07-19 0:46 ` Qu Wenruo
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=20240718225524.GJ8022@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 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.