From: Tom Rini <trini@konsulko.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] inetutils: Import version 1.9.4
Date: Sat, 2 Mar 2019 14:28:37 -0500 [thread overview]
Message-ID: <20190302192837.GJ5026@bill-the-cat> (raw)
In-Reply-To: <ad024f8fb7f7fb2f8bb82a6e878d75a4325565ab.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
On Sat, Mar 02, 2019 at 07:25:29PM +0000, Richard Purdie wrote:
> On Sat, 2019-03-02 at 12:46 -0500, Tom Rini wrote:
> > On Sat, Mar 02, 2019 at 05:00:18PM +0000, Richard Purdie wrote:
> > > On Fri, 2019-03-01 at 17:26 -0500, Tom Rini wrote:
> > > > In order to have more robust stand-alone network tools in oe-
> > > > core,
> > > > bring
> > > > in vim from meta-openembedded/meta-networking. This imports the
> > > > recipes
> > > > as of git commit:
> > > > commit 408204073e6bdcd8ac586e05d5b75213417673f2
> > > > Author: Martin Jansa <martin.jansa@gmail.com>
> > > > Date: Thu Aug 16 20:39:15 2018 +0000
> > > >
> > > > inetutils: fix build with glibc-2.28
> > > >
> > > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > >
> > > vim and inetutils will need entries in maintainers.inc else we'll
> > > see
> > > selftest failures.
> >
> > Ah, OK. Does that generally involve more than ack'ing the automatic
> > upgrades (that one gets CC'd on I assume) and answering questions?
>
> That and helping out with upgrades when new versions appear even if the
> AUH can't handle it.
Yeah, I can handle that much still :) I'll drop myself in for v2. I'll
wait until Monday to give anyone else a chance to chime in on anything
else I might have missed. Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2019-03-02 19:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 22:26 [PATCH 0/4] Introduce packagegroup-core-base-utils Tom Rini
2019-03-01 22:26 ` [PATCH 1/4] vim: Import version 8.1.0347 Tom Rini
2019-03-02 9:15 ` Martin Jansa
2019-03-02 12:36 ` Tom Rini
2019-03-02 12:57 ` Tom Rini
2019-03-02 15:42 ` Joshua Watt
2019-03-01 22:26 ` [PATCH 2/4] inetutils: Import version 1.9.4 Tom Rini
2019-03-02 17:00 ` Richard Purdie
2019-03-02 17:46 ` Tom Rini
2019-03-02 19:25 ` Richard Purdie
2019-03-02 19:28 ` Tom Rini [this message]
2019-03-04 9:47 ` André Draszik
2019-03-04 16:40 ` Tom Rini
2019-03-01 22:26 ` [PATCH 3/4] packagegroup-core-base-utils: Introduce new base-utils packagegroup Tom Rini
2019-03-02 14:41 ` Tom Rini
2019-03-04 16:44 ` Mark Hatle
2019-03-04 18:02 ` Tom Rini
2019-03-01 22:26 ` [PATCH 4/4] imagefeatures: Add test to blacklist building busybox Tom Rini
2019-03-02 7:11 ` [PATCH 0/4] Introduce packagegroup-core-base-utils Adrian Bunk
2019-03-02 12:36 ` Tom Rini
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=20190302192837.GJ5026@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox