[Re: [linux-yocto] [V2-revised] Microchip polarfire SoC - yocto-kernel-cache &
linux-yocto V2 patch.] On 16/11/2023 (Thu 18:24) Kadambathur Subramaniyam,
Saravanan via lists.yoctoproject.org wrote:
> Hi Bruce,
> We have two requests, first one is for linux-yocto and the second one is for
> Yocto-kernel-cache. I received your email about patch corruption and to
> resend
> V3 for the yocto-kernel-cache but this email is meant for linux-yocto.
>
> For the linux-yocto, since it has around 120+ patches i generated PR using
> "git
> request-pull" command and sent through email client(outlook).
Saravanan.K.S,
I am a bit concerned about your workflow, even if Bruce (or git) finally did
manage
to pipe your submission through w3m or ??? Firstly - "outlook" and then...
> For the yocto-kernel-cache today i resent the patch twice to you through "git
> send-email" but still its not delivered to you / linux-yocto mailing list...
The e-mail is not instant. There are moderators involved when there are
people sending who may not be subscribed - or if someone sends 100+
patches at once, a moderator might need to confirm it is not spam. If
you don't wait, check, and confirm - then you risk filling the
maintainer's mailbox with multiple copies, which is not nice.
> PFB the log which i got from my git send-email command. I checked our build
> server by sending git send-email to my email id and i received the email
For the record, the git send-email doesn't really do a lot beyond
looking for a Subject and Date and From line. Beyond that, you can fill
the "to-send" files with complete random noise and they will send.
That said, it really isn't for Bruce to review your process and find
your issues. All this stuff has been solved on-line in hundreds
(thousands?) of forums. But he gave you a giant hint - he wanted v3
in "plain text" - see here:
https://lists.yoctoproject.org/g/linux-yocto/message/13293
There are pages in the kernel covering this:
"No MIME, no links, no compression, no attachments. Just plain text"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n280
When I opened your e-mail in gmail, this is what I saw:
--_000_SJ0PR11MB82969FC0AEA199B8A587ADA1F1B0ASJ0PR11MB8296namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
SGkgQnJ1Y2UsDQpXZSBoYXZlIHR3byByZXF1ZXN0cywgZmlyc3Qgb25lIGlzIGZvciBsaW51eC15
b2N0byBhbmQgdGhlIHNlY29uZCBvbmUgaXMgZm9yIFlvY3RvLWtlcm5lbC1jYWNoZS4gIEkgcmVj
ZWl2ZWQgeW91ciBlbWFpbCBhYm91dCBwYXRjaCBjb3JydXB0aW9uIGFuZCB0byByZXNlbmQgVjMg
Zm9yIHRoZSB5b2N0by1rZXJuZWwtY2FjaGUgYnV0IHRoaXMgZW1haWwgaXMgbWVhbnQgZm9yIGxp
[thousands more similar unreadable lines...]
See that "base64" line? That means it is not plain text. It is encoded.
Once again, the kernel has some info on e-mail clients (like "outlook").
Even without that link, just scroll down your own v3 send. Notice the
font size change between your mail and the one from Bruce? That tells
you that you did not send plain text.
> Let me check and retry sending the yocto-kernel-cache patches to you.
>
> In the meantime could you please help to merge the below pull request for
> linux-yocto?.
I'd suggest you do some more test sends with an internal co-worker
before sending any more large patch series externally. Make 100% sure
they are plain text - not HTML-mail or base64-mail. Bruce has been
generous with his time by "unwinding" the base64 stuff this time, but we
need to do better with future submissions.
Thanks,
Paul.
--
>
> Log:
> skadamba@blr-linux-engg1$git send-email --annotate --subject-prefix="v3]
> [yocto-kernel-cache yocto-6.1][PATCH" --to bruce.ashfi...@gmail.com
> --suppress-cc=all --cc linux-yocto@lists.yoctoproject.org -M yocto-6.1
> /tmp/KrQspiQqYJ/0001-microchip-polarfire-soc-add-configure-file-for-micro.patch
> OK. Log says:
> Sendmail: /usr/sbin/sendmail -i bruce.ashfi...@gmail.com
> linux-yocto@lists.yoctoproject.org
> From: "Saravanan.K.S"
> To: bruce.ashfi...@gmail.com
> Cc: linux-yocto@lists.yoctoproject.org
> Subject: [v3][yocto-kernel-cache yocto-6.1][PATCH] microchip-polarfire-soc:
> add
> configure file for microchip-polarfire-soc BSP in kernel-cache
> Date: Thu, 16 Nov 2023 17:49:19 +
> Message-Id:
> <20231116174919.3056255-1-saravanan.kadambathursubramani...@windriver.com>
> X-Mailer: git-send-email 2.40.0
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
>
> Result: OK
>
> ---
> From: Bruce Ashfield
> Sent: Thursday, November 16, 2023 11:30 PM
> To: Kadambathur Subramaniyam, Saravanan
>
> Cc: linux-yocto@lists.yoctoproject.org
> Subject: Re: [linux-yocto] [V2-revised] Microchip polarfire SoC -
> yocto-kernel-cache & linux-yocto V2 patch.
>
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender
