From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-x86.git branch buildman
Date: Wed, 14 Jan 2015 22:20:06 -0700 [thread overview]
Message-ID: <CAPnjgZ3s2DB6TKnEQGVVD_pJTCZHQFuqT9sYaEPGGsOy4T0UPg@mail.gmail.com> (raw)
Hi Tom,
Can we please try that again? I think I did something wrong. The
branch name is 'buildman'. I am still getting errors about not pushing
the code there, for non-master branches.
The following changes since commit bd5053ffa5b8162257537bdb79ba829372423096:
Merge branch 'buildman' of git://git.denx.de/u-boot-x86 (2015-01-14
11:00:38 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-x86.git
for you to fetch changes up to d2ce658de527af4eaa193ccb7c4d881e02a31257:
buildman: Add an option to write the full build output (2015-01-14
21:16:54 -0800)
----------------------------------------------------------------
Simon Glass (17):
buildman: Add tests that check the correct output directory is used
buildman: Put build in 'current', not 'current/current'
buildman: Don't prune output space for 'current source' build
buildman: Try to guess the upstream commit
buildman: Add an option to flatten output directory trees
buildman: Don't remove entire output directory when testing
buildman: Allow specifying a range of commits to build
buildman: Try to avoid hard-coded string parsing
buildman: Put the toolchain path first instead of last in PATH
buildman: Add an option to use the full tool chain path
buildman: Add a note about Python pre-requisites
buildman: Add documentation about the .buildman file
buildman: Don't complain about missing sections in ~/.buildman
buildman: Don't use the local settings when running tests
buildman: Allow architecture to alias to multiple toolchains
buildman: Add the option to download toolchains from kernel.org
buildman: Add an option to write the full build output
tools/buildman/README | 142 +++++++++++++++++++++++++-----
tools/buildman/bsettings.py | 11 ++-
tools/buildman/builder.py | 21 ++++-
tools/buildman/builderthread.py | 7 +-
tools/buildman/cmdline.py | 10 +++
tools/buildman/control.py | 58 ++++++++++---
tools/buildman/test.py | 75 +++++++++++++++-
tools/buildman/toolchain.py | 270
++++++++++++++++++++++++++++++++++++++++++++++++++++-----
tools/patman/gitutil.py | 90 ++++++++++++++++---
9 files changed, 606 insertions(+), 78 deletions(-)
Regards,
Simon
next reply other threads:[~2015-01-15 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 5:20 Simon Glass [this message]
2015-01-16 15:58 ` [U-Boot] Please pull u-boot-x86.git branch buildman Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2015-04-18 22:23 Simon Glass
2015-04-19 18:28 ` Tom Rini
2014-08-13 14:46 Simon Glass
2014-08-13 15:26 ` Tom Rini
2014-08-13 15:31 ` Simon Glass
2014-08-13 18:00 ` Tom Rini
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=CAPnjgZ3s2DB6TKnEQGVVD_pJTCZHQFuqT9sYaEPGGsOy4T0UPg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.