From: "Sinan Kaya" <okaya@kernel.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH v3] iproute2: split ip to individual package
Date: Wed, 16 Dec 2020 12:09:27 -0500 [thread overview]
Message-ID: <284464d4-6bc6-f70a-4c5e-630cc9fc13b0@kernel.org> (raw)
In-Reply-To: <497c9433b74b13fc96510739deb4b41d2ea2fd5e.camel@linuxfoundation.org>
On 12/16/2020 12:00 PM, Richard Purdie wrote:
> I accept there is a case for splitting out ip, the patch now splits out
> every binary though? That isn't what the commit message says...
I thought of going all the way to split everything since I'm here.
Is your preference to keep ip or have individual packages for the
remaining ?
I can adjust commit and name accordingly.
next prev parent reply other threads:[~2020-12-16 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:45 [meta-oe][PATCH v3] iproute2: split ip to individual package Sinan Kaya
2020-12-16 17:00 ` [OE-core] " Richard Purdie
2020-12-16 17:09 ` Sinan Kaya [this message]
2020-12-16 17:24 ` Richard Purdie
2020-12-16 17:25 ` Sinan Kaya
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=284464d4-6bc6-f70a-4c5e-630cc9fc13b0@kernel.org \
--to=okaya@kernel.org \
--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