From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lrzsz: remove
Date: Fri, 08 Dec 2017 17:46:37 +0000 [thread overview]
Message-ID: <1512755197.19417.115.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0La3_94Rg1LXJ9N81Ss4yoFvm3b3unJ5xt6-wc4p4-BFyQ@mail.gmail.com>
On Fri, 2017-12-08 at 17:05 +0000, Burton, Ross wrote:
> I've had people from the past
What are you suggesting? ;-)
> suggest that this is still useful for deeply embedded environments
> where a serial line is the only form of communication, so I'm
> retracting this and will instead clean up dependencies so it doesn't
> end up in all images.
To be clear, if you have a device you're doing board bringup on and
serial works but network doesn't this does provide a useful way to get
files in/out. That isn't an entirely unknown situation for OE users. It
would also potentially allow us to improve the serial test runner used
by poky-tiny.
Cheers,
Richard
next prev parent reply other threads:[~2017-12-08 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 16:44 [PATCH] lrzsz: remove Ross Burton
2017-12-08 17:05 ` Burton, Ross
2017-12-08 17:46 ` Richard Purdie [this message]
2017-12-09 3:29 ` Bill Randle
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=1512755197.19417.115.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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