From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Collapsing buildman output dir?
Date: Fri, 24 Oct 2014 15:12:40 -0400 [thread overview]
Message-ID: <20141024191240.GQ25506@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ2eKDTHkpdFW0ZxxS-gNfqzd9w_-D_mFPMhRAF39nrTXw@mail.gmail.com>
On Thu, Oct 23, 2014 at 12:28:10PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 23 October 2014 07:03, Tom Rini <trini@ti.com> wrote:
> > Hey,
> >
> > So a common use case for me is building a single board. I've updated my
> > wrapper script from BUILD_DIR=$MACHINE ./MAKEALL $MACHINE (roughly, of
> > course) to:
> > ./tools/buildman/buildman --keep-outputs -dvel --output $MACHINE ^$MACHINE$
> >
> > Which results in my output being ./$MACHINE/current/current/$MACHINE
> > rather than just $MACHINE. Is there a way we can collapse things down
> > easily when we know we aren't going to be building multiple commits?
>
> Are you thinking of a new option to do this?
Well, if we can't just do it automatically, it's probably not worth the
hassle. Probably..
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141024/f3b6898a/attachment.pgp>
next prev parent reply other threads:[~2014-10-24 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 13:03 [U-Boot] Collapsing buildman output dir? Tom Rini
2014-10-23 18:28 ` Simon Glass
2014-10-24 19:12 ` Tom Rini [this message]
2014-10-29 19:22 ` Simon Glass
2014-10-30 8:02 ` Albert ARIBAUD
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=20141024191240.GQ25506@bill-the-cat \
--to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox