From: Zorro Lang <zlang@redhat.com>
To: Ritesh Harjani <ritesh.list@gmail.com>,
"Darrick J . Wong" <djwong@kernel.org>
Cc: fstests <fstests@vger.kernel.org>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop
Date: Fri, 1 Apr 2022 13:30:47 +0800 [thread overview]
Message-ID: <20220401053047.ic4cbsembj6eoibm@zlang-mailbox> (raw)
In-Reply-To: <20220331165335.mzx3gfc3uqeeg3sz@riteshh-domain>
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.
Thanks,
Zorro
>
> -ritesh
>
next prev parent reply other threads:[~2022-04-01 5:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:54 [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 1/4] generic/468: Add another falloc test entry Ritesh Harjani
2022-04-03 23:28 ` Dave Chinner
2022-04-05 11:06 ` Ritesh Harjani
2022-04-05 22:00 ` Theodore Ts'o
2022-04-06 11:52 ` Ritesh Harjani
2022-04-06 4:05 ` Dave Chinner
2022-04-06 11:56 ` Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 2/4] common/punch: Add block_size argument to _filter_fiemap_** Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 3/4] generic/678: Add a new shutdown recovery test Ritesh Harjani
2022-04-03 23:38 ` Dave Chinner
2022-04-05 10:57 ` Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 4/4] generic/679: Add a test to check unwritten extents tracking Ritesh Harjani
2022-04-03 23:43 ` Dave Chinner
2022-04-05 10:56 ` Ritesh Harjani
2022-03-31 14:59 ` [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop Zorro Lang
2022-03-31 16:19 ` Ritesh Harjani
2022-03-31 16:53 ` Ritesh Harjani
2022-04-01 5:30 ` Zorro Lang [this message]
2022-04-01 5:55 ` Ojaswin Mujoo
2022-04-01 17:04 ` Darrick J. Wong
2022-04-02 3:40 ` Zorro Lang
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=20220401053047.ic4cbsembj6eoibm@zlang-mailbox \
--to=zlang@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ritesh.list@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;
as well as URLs for NNTP newsgroup(s).