From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/3] Update upstream tracking information
Date: Thu, 30 Jul 2015 17:00:15 +0300 [thread overview]
Message-ID: <cover.1438263355.git.alexander.kanavin@linux.intel.com> (raw)
This patchset contains the outcome of the upstream tracking review I did for all
oe-core recipes. It consists of many small fixes squashed together: mostly outdated
information being removed, or incorrect information being updated, or missing
information being added.
The following changes since commit d5aebc938a52fee3ca99f2cb0061cbb40cef5200:
distrodata.bbclass: drop the manual upstream version check logic (2015-07-30 16:27:33 +0300)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akanavin/recipe-reporting-fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/recipe-reporting-fixes
Alexander Kanavin (3):
distro_alias.inc: drop reference to Google Code
package_regex.inc: updates to fix upstream version checks for multple
packages
upstream_tracking.inc: remove outdated information
meta-yocto/conf/distro/include/distro_alias.inc | 1 -
meta-yocto/conf/distro/include/package_regex.inc | 145 +++++++++++++++++----
.../conf/distro/include/upstream_tracking.inc | 44 +------
3 files changed, 126 insertions(+), 64 deletions(-)
--
2.1.4
next reply other threads:[~2015-07-30 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 14:00 Alexander Kanavin [this message]
2015-07-30 14:00 ` [PATCH 1/3] distro_alias.inc: drop reference to Google Code Alexander Kanavin
2015-07-30 14:00 ` [PATCH 2/3] package_regex.inc: updates to fix upstream version checks for multple packages Alexander Kanavin
2015-07-30 14:00 ` [PATCH 3/3] upstream_tracking.inc: remove outdated information Alexander Kanavin
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=cover.1438263355.git.alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=poky@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.