Re: [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop

Darrick J. Wong
2022-04-01T17:04:56Z

On Fri, Apr 01, 2022 at 01:30:47PM +0800, Zorro Lang wrote:
> On Thu, Mar 31, 2022 at 10:23:35PM +0530, Ritesh Harjani wrote:
> > On 22/03/31 09:49PM, Ritesh Harjani wrote:
> > > On 22/03/31 10:59PM, Zorro Lang wrote:
> > > > On Thu, Mar 31, 2022 at 06:24:19PM +0530, Ritesh Harjani wrote:
> > > > > Hello,
> > > >
> > > > Hi,
> > > >
> > > > Your below patches looks like not pure text format, they might contain
> > > > binary character or some special characers, looks like the "^M" [1].
> >
> > Sorry to bother you. But here is what I tried.
> > 1. Download the mbx file using b4 am. I didn't see any such character ("^M") in
> > the patches.
> > 2. Saved the patch using mutt. Again didn't see such character while doing
> > cat -A /patch/to/patch
> > 3. Downloaded the mail using eml format from webmail. Here I do see this
> > character appended. But that happens not just for my patch, but for all
> > other patches too.
> >
> > So could this be related to the way you are downloading these patches.
> > Please let me know, if I need to resend these patches again? Because, I don't
> > see this behavior at my end. But I would happy to correct it, if that's not the
> > case.
>
> Hmm... weird, When I tried to open your patch emails, my mutt show me:
>
> [-- application/octet-stream is unsupported (use 'v' to view this part) --]
>
> Then I have to input 'v' to see the patch content. I'm not sure what's wrong,
> this's the 2nd time I hit this "octet-stream is unsupported" issue yesterday.
>
> Hi Darrick, or any other forks, can you open above 4 patches normally? If that's
> only my personal issue, I'll check my side.

There's no application/octet anywhere in the email that I received.
Has your IT department gone rogue^W^Wincreased value-add again?

--D

> Thanks,
> Zorro
>
> >
> > -ritesh
> >
>