From: Jian Liu <jian.liu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] archiver.bbclass: do checkout for kernel
Date: Fri, 18 Dec 2015 11:31:44 +0800 [thread overview]
Message-ID: <56737E20.6000201@windriver.com> (raw)
In-Reply-To: <CAJTo0LYTKAg_oiwxyOzDYPZvRBYs7MEd9qzvPK1fW-jUc4wT_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Hi Ross,
I test this patch. I seem to have no relationship with my issue. This
patch just optimizes some tasks.
My problem seems to be gotten around by a patch
523e4f6a6913b64453579d27a02467e14f7df42e submitted by Bruce.
"bareclone=1" is removed from SRC_URI. So kernel source is not a bare
repo any more.
I do not know why "bareclone=1" is removed. This option seems to have no
side effect on kernel.
So I thinks this should be a hidden trouble.
Do you have any ideas?
Thanks!
Jian
On 2015年12月17日 06:29, Burton, Ross wrote:
>
> On 2 November 2015 at 06:23, Jian Liu <jian.liu@windriver.com
> <mailto:jian.liu@windriver.com>> wrote:
>
> The repo of kernel is bare git repository and we need to checkout
> to get
> the source code.
>
>
> A recent patch to archiver ("fix previous issue regarding work-shared
> for linux-yocto") claims to fix this, can you confirm if that fixes
> this problem or if this fixes more edge cases regarding the kernel.
>
> Cheers,
> Ross
[-- Attachment #2: Type: text/html, Size: 2318 bytes --]
prev parent reply other threads:[~2015-12-18 3:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 6:23 [PATCH] archiver.bbclass: do checkout for kernel Jian Liu
2015-11-02 21:30 ` Khem Raj
2015-11-03 9:22 ` Jian Liu
2015-11-04 5:57 ` Khem Raj
2015-11-05 2:14 ` Jian Liu
2015-11-05 2:22 ` Khem Raj
2015-11-13 8:16 ` Jian Liu
2015-12-14 5:37 ` Jian Liu
2015-12-16 22:29 ` Burton, Ross
2015-12-18 3:31 ` Jian Liu [this message]
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=56737E20.6000201@windriver.com \
--to=jian.liu@windriver.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.