From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.18][PATCH 0/3] Backports for 1.18 branch (cover letter only)
Date: Tue, 3 Dec 2013 16:36:55 +0000 [thread overview]
Message-ID: <cover.1386088140.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit bbb4fa427739912ff3b87379bf629066f6662458:
methodpool: Retire it, remove global method scope (2013-09-11 17:58:14 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bitbake-118-next
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bitbake-118-next
Nicolas Dechesne (1):
bitbake: fetch2/svn.py: use log instead of info to retrieve revision
Richard Purdie (1):
bitbake: perforce: Fix path subdirectory issues
Volker Vogelhuber (1):
bitbake: fetch/hg: Improve user/password handling
lib/bb/fetch2/hg.py | 10 ++++++++--
lib/bb/fetch2/perforce.py | 2 +-
lib/bb/fetch2/svn.py | 14 ++++++++------
3 files changed, 17 insertions(+), 9 deletions(-)
--
1.8.1.2
reply other threads:[~2013-12-03 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1386088140.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox