From: Jonathan Liu <net147@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] util-linux: split libsmartcols into separate sub-package
Date: Wed, 11 Mar 2015 23:37:09 +1100 [thread overview]
Message-ID: <550036F5.8030004@gmail.com> (raw)
In-Reply-To: <CAJTo0LbQA+cRhkjR07cYLA22=tbqqsukfCFCKbOaA1Janpc+og@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On 11/03/2015 11:31 PM, Burton, Ross wrote:
> On 11 March 2015 at 07:00, Jonathan Liu <net147@gmail.com
> <mailto:net147@gmail.com>> wrote:
>
> This avoids util-linux-fdisk pulling in util-linux and all the
> associated sub-packages.
>
>
> util-linux is splitting so many packages and adding sub-packages so
> frequently, could we just do this dynamically?
>
> Ross
Perhaps. I don't have experience in that area.
Regards,
Jonathan
[-- Attachment #2: Type: text/html, Size: 1451 bytes --]
next prev parent reply other threads:[~2015-03-11 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 7:00 [PATCH] util-linux: split libsmartcols into separate sub-package Jonathan Liu
2015-03-11 12:31 ` Burton, Ross
2015-03-11 12:37 ` Jonathan Liu [this message]
2015-03-11 12:55 ` Burton, Ross
2015-03-11 12:56 ` Jonathan Liu
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=550036F5.8030004@gmail.com \
--to=net147@gmail.com \
--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 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.