All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.04 released
Date: Thu, 16 Apr 2015 10:44:13 +0200	[thread overview]
Message-ID: <20150416104413.69bdff0b@lilith> (raw)
In-Reply-To: <20150413172047.GG16702@bill-the-cat>

Hello Tom,

On Mon, 13 Apr 2015 13:20:47 -0400, Tom Rini <trini@ti.com> wrote:
> Hey all,
> 
> I've pushed v2015.04 out to the repository and tarballs should exist
> soon.
> 
> The Kconfig migration is moving along nicely as is the DM work.  This
> has been a good all-around nice set of updates, bug fixes and new board
> and feature support.
> 
> Two last things, to repeat what I said last release.  First, really,
> we're going to deprecate and then remove MAKEALL.  If you've got a
> use-case that's not working with buildman please start yelling now so
> that we can get it addressed (and note that there's stuff ready to come
> in once the merge window is open).

One thing that just hit me is that when a buildman target fails to
build, buildman returns an exist code of 128, which wrecks git bisect.
IOW, I cannot do things like

	git bisect start $bad-commit-id $good-commit-id
	git bisect run tools/buildman/buildman $broken-target

because the first trial where the target fails to build will cause git
bisect to terminate with the message

	bisect run failed:                
	exit code 128 from 'tools/buildman/buildman -o ../build/u-boot/ beagle_x15' is < 0 or >= 128

I haven't seen this mentioned so far, but I may have missed it.

Amicalement,
-- 
Albert.

  parent reply	other threads:[~2015-04-16  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 17:20 [U-Boot] [ANN] U-Boot v2015.04 released Tom Rini
2015-04-13 22:10 ` Simon Glass
2015-04-16  8:44 ` Albert ARIBAUD [this message]
2015-04-17  7:37 ` Wolfgang Denk

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=20150416104413.69bdff0b@lilith \
    --to=albert.u.boot@aribaud.net \
    --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.