<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/dev-manual, branch 1.2_M2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.2_M2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.2_M2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2011-11-25T15:24:19+00:00</updated>
<entry>
<title>documentation/dev-manual/dev-manual-newbie.xml: Updates to Bugzilla use</title>
<updated>2011-11-25T15:24:19+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-23T18:50:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=31c4229d3c0452697c7277f61c77294ffb6d6ebb'/>
<id>urn:sha1:31c4229d3c0452697c7277f61c77294ffb6d6ebb</id>
<content type='text'>
I updated the Bug Tracking section to include rudimentary use of
Bugzilla for entering a new bug.

Fixes [YOCTO #237]

(From yocto-docs rev: 8f2702444812c9dc25195340acebbaae15cd59d7)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation: BB_NUMBER_THREADS and PARALLEL_MAKE suggestions</title>
<updated>2011-11-25T15:24:19+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-16T17:42:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=affc8b985a6b059424ae67e230cdc1f1215c9977'/>
<id>urn:sha1:affc8b985a6b059424ae67e230cdc1f1215c9977</id>
<content type='text'>
Text that suggests setting the BB_NUMBER_THREADS and
PARALLEL_MAKE variables to speed build time has been updated to
suggest a setting of twice the number of host cores supported.

The 2x number came to light through a discussion on the project
mailing list initiated by Robert P. J. Day.

Reported-by: Robert P. J. Day
(From yocto-docs rev: 1846b41a595b7bd905ca828eaa04112d1533d7a1)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual: Edits from Tom Zanussi.</title>
<updated>2011-11-25T15:24:17+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-10T21:28:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=39899b2212a5f21251004757d3c64055046fef11'/>
<id>urn:sha1:39899b2212a5f21251004757d3c64055046fef11</id>
<content type='text'>
Tom Zanussi provided a review up through part of the "model"
chapter.  I have implemented his comments mosty verbatim.

Reported-by: Tom Zanussi
(From yocto-docs rev: 693d4fadd4b34ffef9953fb1850d381ff7c028a3)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation: Changed all manual links to point to "latest"</title>
<updated>2011-11-25T15:24:17+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-10T18:28:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=684c35b7aa0898f95ab70a5982ef74ce98107d93'/>
<id>urn:sha1:684c35b7aa0898f95ab70a5982ef74ce98107d93</id>
<content type='text'>
There are many references to YP documentation throughout the
YP manual set.  They used to have hard-coded links to the
current release (e.g. yoctoproject.org/docs/1.1 for Edison).
This created a situation where if you went to a document on
the website and clicked on a external reference to another
manual, you would redirect to the current manual on the website.
Really, you would want to go to the latest manual, which is
one that is under development.  Changing the links to
"yoctoproject.org/docs/latest" makes the tip of master, which
is used for devloping the next release, always have references
to the manuals being developed and not back to the stable
released set of manuals.

This "latest" and "current" scheme for the links is not perfect.
What has to happen when the latest set of the manuals freezes
and becomes the next stable release, all the links in the docs
will need to be changed from "latest" in the URL to the new
release number.  So for example, all the "latest" occurences
would need to be changed to "1.2".  Then for the next cycle
as development begins again, the links need to be infused with
"latest" again.

(From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation: Standardized on spelling of BitBake</title>
<updated>2011-11-25T15:24:15+00:00</updated>
<author>
<name>Robert P. J. Day</name>
<email>rpjday@crashcourse.ca</email>
</author>
<published>2011-11-09T15:28:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c230114ddd161f046985e761b92d8eff01c3c15'/>
<id>urn:sha1:8c230114ddd161f046985e761b92d8eff01c3c15</id>
<content type='text'>
Robert found five instances where I missed the correct usage of
"BitBake."

(From yocto-docs rev: 0819076e8677accd157497ed4fa33ebab2528044)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual/style.css: Fixed HTML output</title>
<updated>2011-11-08T16:26:33+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-07T21:25:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a756565d42a6d39659156a2c2acb81e097b5cf2f'/>
<id>urn:sha1:a756565d42a6d39659156a2c2acb81e097b5cf2f</id>
<content type='text'>
I increased the font size and darkened the type up for footnote
text.

(From yocto-docs rev: d43e99137c350d68484df6c0a361804d8ccd2877)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual: Fixed PDF Note line breaks</title>
<updated>2011-11-08T16:26:33+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-04T23:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ca38e7ad79b4a5d9a56fcb64d6379580bc5a5a2b'/>
<id>urn:sha1:ca38e7ad79b4a5d9a56fcb64d6379580bc5a5a2b</id>
<content type='text'>
Several notes were not producing a line-break betweent he end
of the note and the start of the next paragraph.  Most work, but
for some reason these did not.  It is a mystery to me.

(From yocto-docs rev: 2c87e0cb781b6d94297dc558504f869bd54a6ad0)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual/style.css: added .footnote element</title>
<updated>2011-11-08T16:26:32+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-04T23:01:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ddb9351bf0b5da30a8e46e5e7027f5a02f7aa6c6'/>
<id>urn:sha1:ddb9351bf0b5da30a8e46e5e7027f5a02f7aa6c6</id>
<content type='text'>
For HTML formatting I added a new element to format the footnote
to pt-8 font.

(From yocto-docs rev: e0dd425a60ca6e1b75406c7711295e732cacebb9)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual/dev-manual-bsp-appendix.xml: Added footnote</title>
<updated>2011-11-08T16:26:32+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-04T23:00:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=468c879a9c3a30596cf5137d53bd222610b24b1d'/>
<id>urn:sha1:468c879a9c3a30596cf5137d53bd222610b24b1d</id>
<content type='text'>
Per Tom Zanussi's suggestion, we added a footnote to the paragraph
instructing the user on build problems for the example.  I don't
have clean fonts in the HTML version of the output.  I am still working
on figuring that out.

Reported by: Tom Zanussi
(From yocto-docs rev: 30fe7bd239292ed92f76fbc2f1fad62469f7fe9b)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>documentation/dev-manual/dev-manual-bsp-appendix.xml: Tom Zanussi edits.</title>
<updated>2011-11-08T16:26:32+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>scott.m.rifenbark@intel.com</email>
</author>
<published>2011-11-04T21:22:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e8f5b17e86818ae6346ed40f0330cb19946ab626'/>
<id>urn:sha1:e8f5b17e86818ae6346ed40f0330cb19946ab626</id>
<content type='text'>
Some wording changes to keep things accurate.  Also inserted some
"&amp;nbsp" characters in some headings to force an extra space between
normal font and courier font words.  It appears the PDF version of
the generated manual shoves these words together with no intervening
space.  Looks like hell.

Reported by: Tom Zanussi
(From yocto-docs rev: 5dcb9ae99f1752599fd56a276ccafd79a52334f8)

Signed-off-by: Scott Rifenbark &lt;scott.m.rifenbark@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
