From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jian Liu <jian.liu@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel-devsrc: Fix backward compaibilty
Date: Wed, 20 Jan 2016 07:52:20 +0000 [thread overview]
Message-ID: <1453276340.27999.141.camel@linuxfoundation.org> (raw)
In-Reply-To: <1453267659-18756-1-git-send-email-jian.liu@windriver.com>
On Wed, 2016-01-20 at 13:27 +0800, Jian Liu wrote:
> kernel-dev is replaced by kernel-devsrc
No, its not.
> , which breaks
> backward compaibilty.
> -- add alias for kernel-devsrc
> -- kernel-devsrc provides the kernel-dev.
> -- remove kernel-dev from the sub-packages of linux-windriver
kernel-dev is useful for things like profiling tools where you need
things like system.Map or the kernel configuration without source code.
If you need the "full" source, you can use kernel-devsrc.
I'm not sure we want to remove kernel-dev given it does have a use?
Cheers,
Richard
next prev parent reply other threads:[~2016-01-20 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 5:27 [PATCH] kernel-devsrc: Fix backward compaibilty Jian Liu
2016-01-20 7:52 ` Richard Purdie [this message]
2016-01-20 8:22 ` Jian Liu
2016-01-20 13:24 ` Bruce Ashfield
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=1453276340.27999.141.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jian.liu@windriver.com \
--cc=openembedded-core@lists.openembedded.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