From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 00/15] More dockersetup/import fixes [cover letter only]
Date: Mon, 30 Sep 2019 11:12:17 +1300 [thread overview]
Message-ID: <cover.1569794507.git.paul.eggleton@linux.intel.com> (raw)
A few more improvements from the Clear Linux Dissector [1] for dockersetup,
import_layers, and update_classic_status.
[1] https://github.com/intel/clear-linux-dissector-web
The following changes since commit b78e498c2086e4cb6631d73f36db059d37ad70ad:
import_layers: fix updating build dependencies (2019-09-17 15:35:44 +1200)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/dissector-backports2
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/dissector-backports2
Paul Eggleton (15):
dockersetup.py: add connectivity check
docker: fix comment at top of Dockerfile
dockersetup: proxy support fixes
dockersetup: add uninstall option
dockersetup: handle ArgumentTypeError properly
dockersetup: allow updating if proxy config set in environment
dockersetup: minor command line comment fix
update_classic_status: tweak single-object queries
update_classic_status: switch to argparse
update_classic_status: add cover status import/export
dockersetup: ensure letsencrypt volume change gets undone
import_layers: use vcs_last_rev to check if record is updated
import_layers: tweak debug logging to be a bit more useful
README.devel: touch up a few things
update_classic_status: ensure fields are correctly ordered
Dockerfile | 4 +-
README.devel | 29 +-
docker/connectivity_check.sh | 35 ++
docker/git-proxy | 10 +-
dockersetup.py | 191 ++++++++--
layerindex/tools/import_layers.py | 12 +-
layerindex/tools/update_classic_status.py | 423 +++++++++++++---------
7 files changed, 481 insertions(+), 223 deletions(-)
create mode 100755 docker/connectivity_check.sh
--
2.20.1
reply other threads:[~2019-09-29 22:12 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.1569794507.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@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.