From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Linux kernel checkpatch.pl mentorship
Date: Thu, 17 Sep 2020 19:11:44 +0530 [thread overview]
Message-ID: <CABJPP5BBUsSQBDi1QbL7xgVdRUqMG7OWXcNSUKsMN601Y3EYbw@mail.gmail.com> (raw)
In-Reply-To: <CABJPP5Dtz7VagfY+h2Qcm=XH6W7EQxXv1QReJLU9pnz2Jp_coQ@mail.gmail.com>
> So you see in all these cases non ascii characters are present. I looked
> into checkpatch.pl .
>
> line 2662:
> if (decode("MIME-Header", $line) =~ /^From:\s*(.*)/) {
> $author = $1;
> $author = encode("utf8", $author) if ($line =~ /=\?utf-8\?/i);
> $author =~ s/"//g;
> $author = reformat_email($author);
> }
>
> When i looked into $line, it gave below:
> From: =?UTF-8?q?=E5=91=A8=E7=90=B0=E6=9D=B0=20=28Zhou=20Yanjie
> =29?=
> <zhouyanjie@wanyeetech.com>
>
> And at the end of this block, $author was equal to ''.
> There seems to be a parsing problem there.
Also I looked into this output more, and I looked into the git
history. For the FROM:
parsing part, the author wrote this:
"Non-ASCII quoted printable encoding in From: headers and (lack of) double
quotes are handled. Split From: headers are not fully handled: only the
the first part is compared."
So the problem instead seems to be the Split From: headers. In all the
cases that I
mentioned, due to formatting issues or something, the email address was
pushed off into the next line, due to which parsing fails.
A solution would be to write logic for handling these Split From:
headers, which the
author left off.
Thanks,
Dwaipayan.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-09-17 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABJPP5CSa_QowD-O3_E5ndoQJvuBv=n2x5WG-acwQKE=rt5+Rw@mail.gmail.com>
[not found] ` <alpine.DEB.2.21.2009110925160.9220@felia>
2020-09-12 9:09 ` [Linux-kernel-mentees] Linux kernel checkpatch.pl mentorship Dwaipayan Ray
2020-09-12 11:03 ` Lukas Bulwahn
2020-09-12 12:08 ` Dwaipayan Ray
2020-09-12 12:21 ` Lukas Bulwahn
2020-09-13 8:16 ` Dwaipayan Ray
2020-09-13 11:05 ` Lukas Bulwahn
[not found] ` <CABJPP5BmRcC+OTSjuX_QrYononVq__DkhjGOgiKrP147MAXK+g@mail.gmail.com>
[not found] ` <alpine.DEB.2.21.2009132015570.6806@felia>
2020-09-13 18:23 ` Dwaipayan Ray
[not found] ` <alpine.DEB.2.21.2009132010300.6806@felia>
2020-09-13 18:39 ` Dwaipayan Ray
2020-09-14 5:17 ` Lukas Bulwahn
2020-09-14 12:31 ` Dwaipayan Ray
2020-09-14 13:49 ` Lukas Bulwahn
2020-09-14 15:39 ` Dwaipayan Ray
2020-09-14 18:32 ` Lukas Bulwahn
2020-09-15 13:04 ` Dwaipayan Ray
2020-09-16 7:01 ` Lukas Bulwahn
2020-09-17 13:09 ` Dwaipayan Ray
2020-09-17 13:41 ` Dwaipayan Ray [this message]
2020-09-17 14:18 ` Lukas Bulwahn
2020-09-17 14:43 ` Dwaipayan Ray
2020-09-17 15:03 ` Lukas Bulwahn
2020-09-17 14:13 ` Lukas Bulwahn
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=CABJPP5BBUsSQBDi1QbL7xgVdRUqMG7OWXcNSUKsMN601Y3EYbw@mail.gmail.com \
--to=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=lukas.bulwahn@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).