On 09/04/2018 03:31 PM, Randy MacLeod wrote:
We really want to get this change merged this week so
that it's part of the 2.6-M3 content that will be well tested.
On 08/31/2018 03:42 AM, Andrej Valek wrote:
I had some network problems.
This patch could be ignored, because, it's same as
http://lists.openembedded.org/pipermail/openembedded-core/2018-August/155059.html
That patch dropped the:
Openpgp: preference=signencrypt
Autocrypt: addr=andrej.va...@siemens.com; prefer-encrypt=mutual;
keydata=
xsBNBFkSzTcBCADSJTRk7Y...bIFUmc7ck3KeuUGKy
ifrpWD6/7YPXbixv4sAlFl...zmMdr0BPLMsL96nBO
...
but it's still base64 encoded:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
whereas other patches to the list use:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Can you fix that and/or send a pull request:
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Committing_your_patch
Andrej,
Apparently, I need to learn how to handle base64 encoded patches since
Richard managed to merge this to master today...
Ah, using patchworks does it for me.
FYI, just use the download link on:
https://patchwork.openembedded.org/patch/154457/
as mentioned here:
https://stackoverflow.com/questions/5062389/how-to-use-git-am-to-apply-patches-from-email-messages
I'd still prefer to only deal with clear text patches on the list.
Baring that, one should be able to handle base64 encoded patches
without patchworks in case anyone has read this far and knows how
to do that...
../Randy
Thanks,
--
# Randy MacLeod
# Wind River Linux
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
