public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] [PATCH 0/6] Various changes towards 3.0 branch
Date: Wed, 10 Sep 2014 21:01:02 -0700	[thread overview]
Message-ID: <1410408068-3441-1-git-send-email-dolsen@gentoo.org> (raw)

Another convienence grouping of various patches.  
This is the last 6 patches remaining in the pending branch at this time.
Once these 3 patch series are caught up, I'll move more from 3.0 into pending.

Brian Dolbec (6):
  FIXME! Comment out a small code block causing TypeError.
  Break out more repeated (path1 + path2)'s...
  Rename a make.conf key to make_conf due to bash variable name
    restrictions
  reduce 2 operations into one simpler one
  Extend ParserBase to do variable substitution.
  Make shdir a complete path to ease it's use.

 catalyst/base/stagebase.py                        | 45 ++++++++++++-----------
 catalyst/config.py                                |  9 ++---
 catalyst/defaults.py                              |  4 +-
 catalyst/lock.py                                  | 23 +++++++++---
 catalyst/main.py                                  |  6 ++-
 etc/catalyst.conf                                 |  8 +++-
 targets/embedded/embedded-controller.sh           | 22 +++++------
 targets/grp/grp-controller.sh                     |  6 +--
 targets/livecd-stage1/livecd-stage1-controller.sh |  4 +-
 targets/livecd-stage2/livecd-stage2-controller.sh | 22 +++++------
 targets/netboot/netboot-combine.sh                |  6 +--
 targets/netboot/netboot-controller.sh             | 24 ++++++------
 targets/netboot2/netboot2-controller.sh           | 16 ++++----
 targets/stage1/stage1-controller.sh               |  8 ++--
 targets/stage2/stage2-controller.sh               |  6 +--
 targets/stage3/stage3-controller.sh               |  6 +--
 targets/stage4/stage4-controller.sh               | 22 +++++------
 targets/support/bootloader-setup.sh               |  6 +--
 targets/support/create-iso.sh                     |  4 +-
 targets/support/functions.sh                      |  2 +-
 targets/support/netboot2-final.sh                 |  4 +-
 targets/support/target_image_setup.sh             |  4 +-
 targets/tinderbox/tinderbox-controller.sh         |  6 +--
 23 files changed, 142 insertions(+), 121 deletions(-)

-- 
2.1.0



             reply	other threads:[~2014-09-11  4:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  4:01 Brian Dolbec [this message]
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 1/6] FIXME! Comment out a small code block causing TypeError Brian Dolbec
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 2/6] Break out more repeated (path1 + path2)'s Brian Dolbec
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 3/6] Rename a make.conf key to make_conf due to bash variable name restrictions Brian Dolbec
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 4/6] reduce 2 operations into one simpler one Brian Dolbec
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 5/6] Extend ParserBase to do variable substitution Brian Dolbec
2014-09-11  4:01 ` [gentoo-catalyst] [PATCH 6/6] Make shdir a complete path to ease it's use Brian Dolbec

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=1410408068-3441-1-git-send-email-dolsen@gentoo.org \
    --to=dolsen@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.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