<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bb/parse/parse_py/ConfHandler.py, branch edison-6.0</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=edison-6.0</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=edison-6.0'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2011-07-21T10:09:47+00:00</updated>
<entry>
<title>parse/ConfHandler: Fix multiline variable corruption</title>
<updated>2011-07-21T10:09:47+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-07-20T21:51:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1df5ab5ee285b3220348ce0cf371b81446d55832'/>
<id>urn:sha1:1df5ab5ee285b3220348ce0cf371b81446d55832</id>
<content type='text'>
When parsing multiline variables in conf files, the last character can
be accidentally removed. s2 contains new data read from the file which
may or may not end with the continuation character. It makes sense to
let the next loop iteration strip this if needed.

We don't often use multiline expressions in .conf files which is why I'd
imagine we haven't noticed this before. Most variables are quoted and
its the closing quotation which often disappears.

(Bitbake rev: 09a9146262d58dfe4a2ea4270026b90ae33f6c91)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>parse: pass filename, lineno into the ast</title>
<updated>2011-01-10T13:24:03+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2011-01-04T20:34:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b127874ee6f7b8801575a10f4b7df02783aafdeb'/>
<id>urn:sha1:b127874ee6f7b8801575a10f4b7df02783aafdeb</id>
<content type='text'>
We will be needing this information to improve the tracebacks of python code
from the metadata, as well as to give the user information about where
variables were defined, so they know how it ended up the way it is.

(Bitbake rev: 9615c538b894f71a2d1a0ba6b3f260db91e75786)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ConfHandler: commentary typo fixes</title>
<updated>2011-01-04T15:00:25+00:00</updated>
<author>
<name>Bernhard Reutner-Fischer</name>
<email>rep.dot.nop@gmail.com</email>
</author>
<published>2011-01-03T19:57:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=641fc9bad076333a0881910d804a8f267f073515'/>
<id>urn:sha1:641fc9bad076333a0881910d804a8f267f073515</id>
<content type='text'>
(Bitbake rev: 089dc31932a85455ed0fec8209d0451af4310f94)

Signed-off-by: Bernhard Reutner-Fischer &lt;rep.dot.nop@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Switch bitbake internals to use logging directly rather than bb.msg</title>
<updated>2011-01-04T14:46:33+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-06-10T17:35:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ecc68fa4fbb579e97ea45156e79a293b073697a0'/>
<id>urn:sha1:ecc68fa4fbb579e97ea45156e79a293b073697a0</id>
<content type='text'>
We use a custom Logger subclass for our loggers

This logger provides:
- 'debug' method which accepts a debug level
- 'plain' method which bypasses log formatting
- 'verbose' method which is more detail than info, but less than debug

(Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Move the unset BBPATH sanity check after the bblayers processing</title>
<updated>2010-07-02T14:41:33+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-04-14T21:27:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dc39ebe91eabc48517aaac98655e50c7b1702262'/>
<id>urn:sha1:dc39ebe91eabc48517aaac98655e50c7b1702262</id>
<content type='text'>
This way we can fully utilize bblayers, you can do everything in bblayers.conf
and avoid setting any environment variables at all.

(Bitbake rev: 5def1c8c31432968349f9b29d6333d7962260a8b)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Apply some 2to3 transforms that don't cause issues in 2.6</title>
<updated>2010-07-02T14:41:33+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-04-12T00:03:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1180bab54e2879401f3586c91a48174191a1ee8b'/>
<id>urn:sha1:1180bab54e2879401f3586c91a48174191a1ee8b</id>
<content type='text'>
(Bitbake rev: d39ab776e7ceaefc8361150151cf0892dcb70d9c)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Import fixups</title>
<updated>2010-07-02T14:41:32+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-04-08T17:22:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1c74fd768f8e4f5778411538b906cdcc22fe3f67'/>
<id>urn:sha1:1c74fd768f8e4f5778411538b906cdcc22fe3f67</id>
<content type='text'>
(Bitbake rev: 4fa052f426e3205ebace713eaa22deddc0420e8a)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Formatting cleanups</title>
<updated>2010-07-02T14:41:32+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-03-24T23:56:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7acc132cac873e60005516272473a55a8160b9c4'/>
<id>urn:sha1:7acc132cac873e60005516272473a55a8160b9c4</id>
<content type='text'>
(Bitbake rev: 2caf134b43a44dad30af4fbe33033b3c58deee57)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Stop using functions via 'bb' that were moved from there to other modules</title>
<updated>2010-07-02T14:41:32+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-04-10T00:11:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6623d79adaf445081e68b307355292077800d4f4'/>
<id>urn:sha1:6623d79adaf445081e68b307355292077800d4f4</id>
<content type='text'>
(Bitbake rev: 03a6c26f8da226f442c3cab557e4733f7cd6eeac)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Ensure we always utilize the correct messaging domains</title>
<updated>2010-07-02T14:41:31+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-04-09T19:33:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=87f62d7c8d386df0d613da4f48c0b210902ab621'/>
<id>urn:sha1:87f62d7c8d386df0d613da4f48c0b210902ab621</id>
<content type='text'>
(Bitbake rev: 92a2e2e90981c0615171abe03645a772d84f6986)

Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
</feed>
