All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [Daisy - Initial Pull 0/9] Please Review
Date: Fri, 23 May 2014 09:40:16 -0700	[thread overview]
Message-ID: <cover.1400862889.git.sgw@linux.intel.com> (raw)

Richard,

This is a set of fixes that I backported from 1.7 for Daisy.

Sau!

The following changes since commit fe083b674b20b254877a6d8249b11c9a7373866e:

  bitbake-user-manual-hello.xml: Edits to the "Hello World" Appendix. (2014-04-21 22:51:42 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib sgw/bitbake-1.22
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgw/bitbake-1.22

Jacob Kroon (1):
  bitbake: bitbake-diffsigs: Fix runtime error when no arguments are
    given

Nick Lewis (1):
  bitbake: Fix refetch of local files when they are read only

Richard Purdie (5):
  bitbake: runqueue: Fix handling of zero priority task
  bitbake: runqueue: Fix task weighting algorithm
  bitbake: fetch2/git: Stop git from triggering fsync() calls
  bitbake: fetch2/perforce: Ensure command has a default
  bitbake: data_smart: Fix an unusual variable reference bug

Volker Vogelhuber (2):
  bitbake: HG Fetch with username and password in url
  bitbake: fix cloning of mercurial repository with username and
    password specified in url

 bin/bitbake-diffsigs      | 4 ++--
 lib/bb/data_smart.py      | 2 +-
 lib/bb/fetch2/__init__.py | 4 ++--
 lib/bb/fetch2/git.py      | 4 ++--
 lib/bb/fetch2/hg.py       | 7 +++++--
 lib/bb/fetch2/perforce.py | 8 ++++----
 lib/bb/runqueue.py        | 6 +++---
 lib/bb/tests/data.py      | 5 +++++
 8 files changed, 24 insertions(+), 16 deletions(-)

-- 
1.8.3.1



             reply	other threads:[~2014-05-23 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 16:40 Saul Wold [this message]
2014-05-29 12:21 ` [Daisy - Initial Pull 0/9] Please Review Richard Purdie

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.1400862889.git.sgw@linux.intel.com \
    --to=sgw@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 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.