On Sat, May 07, 2022 at 01:26:20PM +0530, Rishabh Dave wrote:
> On Sat, 7 May 2022 at 13:00, Zorro Lang <zlang@xxxxxxxxxx> 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@xxxxxxxxxxxxxxx/
> >
> > 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@xxxxxxxxxxxxxxx/
>
