<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-oe/recipes-support/picocom, branch hardknott</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=hardknott</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=hardknott'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2021-11-13T15:45:48+00:00</updated>
<entry>
<title>recipes: Update SRC_URI branch and protocols</title>
<updated>2021-11-13T15:45:48+00:00</updated>
<author>
<name>Armin Kuster</name>
<email>akuster808@gmail.com</email>
</author>
<published>2021-11-07T18:42:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=7fbb2767186a4db729efe4f440cc9a992f2ab183'/>
<id>urn:sha1:7fbb2767186a4db729efe4f440cc9a992f2ab183</id>
<content type='text'>
This patch updates SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls as generated by the conversion script
in OE-Core.

Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>picocom: update to 3.1</title>
<updated>2019-07-15T15:00:06+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2019-07-15T02:50:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=c1ecd778cef733caf1e3b0ced7fd4da21f080e6d'/>
<id>urn:sha1:c1ecd778cef733caf1e3b0ced7fd4da21f080e6d</id>
<content type='text'>
There have been a couple of releases since we last upgraded, including
a number of additional features. Changelog is here:

  https://github.com/npat-efault/picocom/releases

Also tweak SUMMARY - I don't think this has been 20k in a while; with
this upgrade the binary alone went from 60k to 70k.

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>picocom: Upgrade to 2.2</title>
<updated>2017-04-05T17:28:29+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2017-03-18T17:44:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=2d5b14144e895971254bc2d453386d76183fd3b1'/>
<id>urn:sha1:2d5b14144e895971254bc2d453386d76183fd3b1</id>
<content type='text'>
Package has moved to github
License file got some cosmetic changes see
https://github.com/npat-efault/picocom/commit/13fd331d410c2e8c39fa041bd54c3b0a93df64e1

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>picocom: Fix build</title>
<updated>2017-02-13T17:43:19+00:00</updated>
<author>
<name>Marek Vasut</name>
<email>marex@denx.de</email>
</author>
<published>2017-01-20T10:59:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=d77049facb76c9372101ccaa38e6f0523cf6c05d'/>
<id>urn:sha1:d77049facb76c9372101ccaa38e6f0523cf6c05d</id>
<content type='text'>
The picocom complains about missing GNU_HASH from the binary during
QA stage, this is because the picocom Makefile overrides CPPFLAGS,
CFLAGS and LDFLAGS. Fix this by passing those as an argument to make.
Moreover, since picocom 1.7 now accepts VERSION variable and the
UUCP_LOCK_DIR is set to /var/lock by default, drop the CPPFLAGS
override altogether and replace it simply with passing VERSION
argument to make to precisely retain the original intention.

Signed-off-by: Marek Vasut &lt;marex@denx.de&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>picocom: fix PN -&gt; BPN for multilib</title>
<updated>2015-05-13T12:32:01+00:00</updated>
<author>
<name>Yi Zhao</name>
<email>yi.zhao@windriver.com</email>
</author>
<published>2015-05-08T07:42:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=7c9b9e27b3c267c1f815bb8a794ad84972cb0354'/>
<id>urn:sha1:7c9b9e27b3c267c1f815bb8a794ad84972cb0354</id>
<content type='text'>
Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>picocom: update to 1.7</title>
<updated>2015-01-08T10:58:43+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2015-01-05T11:00:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=bd073fd6dcb9444b24eaa51fb05e03c31b960d4b'/>
<id>urn:sha1:bd073fd6dcb9444b24eaa51fb05e03c31b960d4b</id>
<content type='text'>
Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues</title>
<updated>2014-02-23T22:20:02+00:00</updated>
<author>
<name>Matthieu CRAPET</name>
<email>Matthieu.CRAPET@ingenico.com</email>
</author>
<published>2014-02-19T14:47:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=c95e155780a0cf3a8fb59a2f86db6367d18116fc'/>
<id>urn:sha1:c95e155780a0cf3a8fb59a2f86db6367d18116fc</id>
<content type='text'>
Changes:
- rename SUMMARY with length &gt; 80 to DESCRIPTION
- rename DESCRIPTION with length &lt; 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line

Note: don't bump PR

Signed-off-by: Matthieu Crapet &lt;Matthieu.Crapet@ingenico.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: Unify indentation</title>
<updated>2013-04-15T14:23:17+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2013-04-13T20:49:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=a45830a39bb47a9eab27980d52966226c9504ea4'/>
<id>urn:sha1:a45830a39bb47a9eab27980d52966226c9504ea4</id>
<content type='text'>
* This change is only aesthetic (unlike indentation in Python
  tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
  tabs is the need to update a lot of recipes). Lately this advice
  was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
  error prone when someone is not sure if e.g.
  do_generate_toolchain_file() is Python or shell task and also allows
  to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
  potentially bad (shouldn't be used for indenting of multiline
  variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
  we're quite inconsistent wheater it's first character on line
  under opening quote or under first non-whitespace character in
  previous line.

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Acked-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</content>
</entry>
<entry>
<title>picocom: import from meta-smartphone/meta-shr</title>
<updated>2012-01-23T15:23:12+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2012-01-23T08:49:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=46ea6113c636a480482d968b160cc22d28e1663d'/>
<id>urn:sha1:46ea6113c636a480482d968b160cc22d28e1663d</id>
<content type='text'>
* meta-smartphone/7f797c8e54dd4ec28d75269e80573f45069eebb4
* PR and PRIORITY fields dropped

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
</feed>
