From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/17] buildman: A few more features and improvements (Christmas edition)
Date: Wed, 10 Dec 2014 11:58:05 -0800 [thread overview]
Message-ID: <5488A5CD.2020209@broadcom.com> (raw)
In-Reply-To: <CAPnjgZ2B=2p60zBgFX9v5zKi=zutc14WxXv90sUcid-QRHOkPw@mail.gmail.com>
good improvements -- and it fixes my issues....
Thanks!
(tested buildman-working 6c7f1b6)
Tested-by: Steve Rae <srae@broadcom.com>
On 14-12-09 09:29 PM, Simon Glass wrote:
> Hi,
>
> On 1 December 2014 at 17:50, Simon Glass <sjg@chromium.org> wrote:
>> Hi,
>>
>> On 1 December 2014 at 17:33, Simon Glass <sjg@chromium.org> wrote:
>>> Various people (on CC) have suggested improvements and reported bugs in
>>> buildman. I've done a pass through these and this series is the result.
>>> In summary the main changes are:
>>>
>>> - Flatten the output tree for 'current source builds'
>>> - Improve docs to talk about Python environment and ~/.buildman file
>>> - Toolchain path improvements and changes
>>> - Download and install a new toolchain automatically
>>> - Guess the upstream commit instead of requiring it to be set
>>> - Access to the full build output
>>> - Support for building an arbitrary range of commits
>>
>> This series is available at u-boot-x86/buildman-working.
>>
>> Regards,
>> Simon
>
> Any testing on this? We could perhaps apply some of the doc updates
> and fixes for this release.
>
> Regards,
> Simon
>
prev parent reply other threads:[~2014-12-10 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 0:33 [U-Boot] [PATCH 0/17] buildman: A few more features and improvements (Christmas edition) Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 01/17] buildman: Add tests that check the correct output directory is used Simon Glass
2014-12-16 4:54 ` Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 02/17] buildman: Put build in 'current', not 'current/current' Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 03/17] buildman: Don't prune output space for 'current source' build Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 04/17] buildman: Try to guess the upstream commit Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 05/17] buildman: Add an option to flatten output directory trees Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 06/17] buildman: Don't remove entire output directory when testing Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 07/17] buildman: Allow specifying a range of commits to build Simon Glass
2014-12-14 17:30 ` Daniel Schwierzeck
2014-12-02 0:33 ` [U-Boot] [PATCH 08/17] buildman: Try to avoid hard-coded string parsing Simon Glass
2014-12-02 0:33 ` [U-Boot] [PATCH 09/17] buildman: Put the toolchain path first instead of last in PATH Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 10/17] buildman: Add an option to use the full tool chain path Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 11/17] buildman: Add a note about Python pre-requisites Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 12/17] buildman: Add documentation about the .buildman file Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 13/17] buildman: Don't complain about missing sections in ~/.buildman Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 14/17] buildman: Don't use the local settings when running tests Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 15/17] buildman: Allow architecture to alias to multiple toolchains Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 16/17] buildman: Add the option to download toolchains from kernel.org Simon Glass
2014-12-02 0:34 ` [U-Boot] [PATCH 17/17] buildman: Add an option to write the full build output Simon Glass
2014-12-02 0:50 ` [U-Boot] [PATCH 0/17] buildman: A few more features and improvements (Christmas edition) Simon Glass
2014-12-10 5:29 ` Simon Glass
2014-12-10 19:58 ` Steve Rae [this message]
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=5488A5CD.2020209@broadcom.com \
--to=srae@broadcom.com \
--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.