From: "Denys Dmytriyenko" <denis@denix.org>
To: Paul Barker <pbarker@konsulko.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] External toolchain support
Date: Fri, 12 Jun 2020 00:30:00 -0400 [thread overview]
Message-ID: <20200612043000.GK17660@denix.org> (raw)
In-Reply-To: <CAM9ZRVsT0nuMen2zC_L=+nadg5w0=xj2m8Tp7GR1xL-txzhbjQ@mail.gmail.com>
On Thu, Jun 11, 2020 at 10:27:50AM +0100, Paul Barker wrote:
> On Thu, 11 Jun 2020 at 03:01, Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > All,
>
> Denys,
>
> Thanks for the context here, it's really valuable to understand how
> things have developed. I'd prefer that things improve slowly than that
> we have a breaking fork.
Thank your for understanding!
> Can we identify which of the proposed changes can be made with low
> risk? I think fixing the readme and licensing at least should be
> straightforward.
I guess those can be considered low-impact.
> I'll look at the archiver support myself and see if I can find a
> solution for that.
That would be nice, thanks
--
Denys
next prev parent reply other threads:[~2020-06-12 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:03 External toolchain support Paul Barker
2020-05-20 5:18 ` [meta-arm] " Denys Dmytriyenko
2020-05-20 10:13 ` William Mills
2020-05-20 15:33 ` Sumit Garg
2020-05-20 16:02 ` Paul Barker
2020-05-22 12:59 ` Sumit Garg
2020-06-11 2:01 ` Denys Dmytriyenko
2020-06-11 9:27 ` Paul Barker
2020-06-12 4:30 ` Denys Dmytriyenko [this message]
2020-06-11 14:14 ` Sumit Garg
2020-06-12 5:34 ` Denys Dmytriyenko
2020-06-12 9:55 ` Sumit Garg
[not found] ` <1617B50A09B8150A.14082@lists.yoctoproject.org>
2020-06-12 7:06 ` Denys Dmytriyenko
2020-06-12 10:01 ` Sumit Garg
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=20200612043000.GK17660@denix.org \
--to=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.org \
--cc=pbarker@konsulko.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 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.