From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] opkg: Add upstream fixes
Date: Fri, 22 Nov 2019 08:58:35 +0000 [thread overview]
Message-ID: <0e33e0aac09ea020a6a3d0714a9de15cf07d6f66.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1soT1CqsRqkVOfpGjuCjvvHOExnwjZguXEog9Sa6dc_uFw@mail.gmail.com>
On Thu, 2019-11-21 at 16:27 -0800, Khem Raj wrote:
> On Thu, Nov 21, 2019 at 7:02 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > .../opkg/opkg/open_inner.patch | 150
> > ++++++++++++++++
> > .../opkg/opkg/opkg_archive.patch | 160
> > ++++++++++++++++++
> >
> > +X-Evolution-Source: 1525863794.3857.16@hex
> > +Content-Transfer-Encoding: 8bit
>
> Perhaps this raw mail header can be removed it seems to add no value
> moreover is distracting
Yes, I realised and it was gone in the second version.
Cheers,
Richard
prev parent reply other threads:[~2019-11-22 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 15:02 [PATCH 1/3] opkg: Add upstream fixes Richard Purdie
2019-11-21 15:02 ` [PATCH 2/3] opkg-utils: Fix silent empty/broken opkg package creation Richard Purdie
2019-11-21 15:02 ` [PATCH 3/3] sanity: Add check for tar older than 1.28 Richard Purdie
2019-11-21 15:50 ` Adrian Bunk
2019-11-21 16:54 ` Richard Purdie
2019-11-21 17:02 ` Alexander Kanavin
2019-11-21 17:09 ` Adrian Bunk
2019-11-21 18:09 ` Richard Purdie
2019-11-21 19:14 ` Mark Hatle
2019-11-21 19:33 ` Richard Purdie
2019-11-22 0:27 ` [PATCH 1/3] opkg: Add upstream fixes Khem Raj
2019-11-22 8:58 ` Richard Purdie [this message]
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=0e33e0aac09ea020a6a3d0714a9de15cf07d6f66.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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