Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>, Koen Kooi <koen@beagleboard.org>
Subject: Re: [PATCH] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules
Date: Tue, 15 Mar 2011 18:23:58 +0000	[thread overview]
Message-ID: <1300213438.30423.1820.camel@rex> (raw)
In-Reply-To: <AANLkTikC7yWvzTzf1Od2WLiBhQjz1iactGCaPCN+aAmR@mail.gmail.com>

On Tue, 2011-03-15 at 10:24 -0700, Khem Raj wrote:
> On Tue, Mar 15, 2011 at 10:07 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> >
> > What are the ownership and perms on those?
> >
> > I suppose we could avoid the .pc directory - but it's going to require
> > something more than cp or some additional scripting. Something like tar's
> > exclude functionality might be needed - but I hate to add the intermediate
> > step as the kernel recipes are already so slow.
> 
> 
> hmmm I wonder why those are marked non readable in .pc directory  that
> seems wrong to me

Its quilt that does this. Kind of annoying but its been doing that for a
few versions now...

Cheers,

Richard




  reply	other threads:[~2011-03-15 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  7:25 [PATCH] [RFC] kernel: rework kernel and module classes to allow for building out-of-tree modules Darren Hart
2011-03-15  8:31 ` Koen Kooi
2011-03-15 17:07   ` Darren Hart
2011-03-15 17:24     ` Khem Raj
2011-03-15 18:23       ` Richard Purdie [this message]
2011-03-15 19:27         ` Darren Hart
2011-03-15 19:34           ` Richard Purdie
2011-03-15 20:01             ` Darren Hart
2011-03-16  2:02           ` Khem Raj
2011-03-15 17:25     ` Koen Kooi
2011-03-16  6:50       ` Darren Hart

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=1300213438.30423.1820.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dvhart@linux.intel.com \
    --cc=koen@beagleboard.org \
    --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