[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220331165335.mzx3gfc3uqeeg3sz@riteshh-domain>
Date: Thu, 31 Mar 2022 22:23:35 +0530
From: Ritesh Harjani <ritesh.list@...il.com>
To: fstests <fstests@...r.kernel.org>, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
"Darrick J . Wong" <djwong@...nel.org>
Subject: Re: [PATCHv3 0/4] generic: Add some tests around journal
replay/recoveryloop
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.
-ritesh
Powered by blists - more mailing lists