From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>, <ross.burton@intel.com>
Subject: [PATCH 0/1] package_manager.py: fix bitbake package-index failed
Date: Tue, 13 Sep 2016 04:48:31 -0400 [thread overview]
Message-ID: <cover.1473756300.git.hongxu.jia@windriver.com> (raw)
The following changes since commit 2679a347c576f5411fbe802d2f6201c94036ecb2:
maintainers.inc: rename gtk-doc-stub to gtk-doc, reassign to me (2016-09-09 12:12:59 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib hongxu/package-index
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=hongxu/package-index
Hongxu Jia (1):
package_manager.py: fix bitbake package-index failed
meta/lib/oe/package_manager.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.8.1
next reply other threads:[~2016-09-13 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:48 Hongxu Jia [this message]
2016-09-13 8:48 ` [PATCH 1/1] package_manager.py: fix bitbake package-index failed Hongxu Jia
2016-09-13 14:49 ` Mark Hatle
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.1473756300.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox