All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Andrej Valek <andrej.valek@siemens.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: update to 1.29.2
Date: Wed, 5 Sep 2018 20:05:26 -0400	[thread overview]
Message-ID: <1a6e57df-433a-b7e4-cc6c-d6d8c1b0c43a@windriver.com> (raw)
In-Reply-To: <fe5d1e09-7923-61e7-9bab-6238de83de8e@windriver.com>

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.valek@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


  reply	other threads:[~2018-09-06  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 15:57 [PATCH] busybox: update to 1.29.2 Andrej Valek
2018-08-31  7:42 ` Andrej Valek
2018-09-04 19:31   ` Randy MacLeod
2018-09-06  0:05     ` Randy MacLeod [this message]
2018-09-06 10:38       ` Richard Purdie
2018-08-30 16:02 Andrej Valek

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=1a6e57df-433a-b7e4-cc6c-d6d8c1b0c43a@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=andrej.valek@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.