From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Darren Hart <dvhart@linux.intel.com>,
Chris Larson <clarson@kergoth.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Subject: Re: Documentation: Default FILESDIR
Date: Thu, 01 Mar 2012 15:47:32 +0000 [thread overview]
Message-ID: <3099377.EvlgWZpSHF@helios> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123793B741DAC@ORSMSX101.amr.corp.intel.com>
On Thursday 01 March 2012 15:36:27 Rifenbark, Scott M wrote:
> Please look at
> http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.htm
> l#platdev-appdev-insitu in the YP Reference manual. This is the section you
> refer to in this mail. The link in this latest version correctly goes to
> the referenced Quilt section, which has significantly changed. The little
> paragraph you quote below is now basically part of the 9-step Quilt process
> in the YP Dev manual
> (http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-a
> -quilt-workflow).
>
> Can you look at these two sections now and then provide me with FILESPATH
> information so I can create a glossary entry for the item and possibly work
> the use of FILESPATH into the updated Quilt section?
I think additional file paths are outside the scope of the Quilt section
itself, but it could easily link to a separate section that does discuss it.
It's worth noting though that we tend not to modify FILESPATH directly
anymore; instead we use FILESEXTRAPATHS. I believe there are examples of using
this in the BSP guide, although we do still need to have this documented in
the reference manual.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-01 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:11 Documentation: Default FILESDIR Darren Hart
2012-03-01 0:27 ` Chris Larson
2012-03-01 0:39 ` Darren Hart
2012-03-01 15:36 ` Rifenbark, Scott M
2012-03-01 15:47 ` Paul Eggleton [this message]
2012-03-01 19:17 ` Darren Hart
2012-03-05 11:19 ` Joshua Immanuel
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=3099377.EvlgWZpSHF@helios \
--to=paul.eggleton@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=dvhart@linux.intel.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=yocto@yoctoproject.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 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.