From: Zorro Lang <zlang@redhat.com>
To: Rishabh Dave <ridave@redhat.com>
Cc: fstests@vger.kernel.org, Jeff Layton <jlayton@redhat.com>,
Rishabh Dave <rishabhddave@gmail.com>
Subject: Re: [PATCHv2] cephfs: add ceph-fuse suport for ceph-fuse
Date: Sat, 7 May 2022 16:41:00 +0800 [thread overview]
Message-ID: <20220507084100.75m2ncu247mbt2wi@zlang-mailbox> (raw)
In-Reply-To: <CA+jMu4SNSPtSPyZ+Hv5nC_sJhptj=iM6z4_3C3EZ2FzhTjDOSg@mail.gmail.com>
On Sat, May 07, 2022 at 01:26:20PM +0530, Rishabh Dave wrote:
> On Sat, 7 May 2022 at 13:00, Zorro Lang <zlang@redhat.com> wrote:
> >
> > This patch has been merged, refer to 1dac95cb ("cephfs: add ceph-fuse suport
> > for ceph-fuse") in fstests for-next branch. And I've helped to fix that ";;"
> > missing problem.
> >
> > The release [ANNOUNCE] is:
> > https://lore.kernel.org/fstests/20220430190921.7BC56C385A7@smtp.kernel.org/
> >
> > If you need to fix more issues, please write new patch base on the latest
> > fstests for-next branch.
> >
>
> Okay. Thanks for the fix and thanks for the merge.
>
> Is merging in the for-next branch as good as merging in the master? Or
> should I watch out for my commit until it merges in master?
fstests for-next is an offical branch with PGP signed release version tag,
feel free to prioritize using it. The master branch will be 1~2 weeks later than
for-next, to keep the stability of it. So for-next is fresher, master trys to
be slower and stabler. I explained in last [ANNOUNCE] email [1].
Thanks,
Zorro
[1]
https://lore.kernel.org/fstests/20220430190921.7BC56C385A7@smtp.kernel.org/
>
prev parent reply other threads:[~2022-05-07 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:01 [PATCHv2] cephfs: add ceph-fuse suport for ceph-fuse Rishabh Dave
2022-05-07 7:29 ` Zorro Lang
2022-05-07 7:56 ` Rishabh Dave
2022-05-07 8:41 ` Zorro Lang [this message]
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=20220507084100.75m2ncu247mbt2wi@zlang-mailbox \
--to=zlang@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jlayton@redhat.com \
--cc=ridave@redhat.com \
--cc=rishabhddave@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