public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2011.06 release, Merge Window is OPEN
Date: Tue, 28 Jun 2011 17:24:16 +0200	[thread overview]
Message-ID: <20110628152416.GC31789@bee.dooz.org> (raw)
In-Reply-To: <20110628105542.8BB8015AAEBE@gemini.denx.de>

On Tue, Jun 28, 2011, Wolfgang Denk wrote:
> - The cleanup after the reorganization of the ARM code has not been
>   completed yet. At the moment, approapprox, 100+ ARM boards are
>   *broken* and *do not compile*.
> 
>   Board maintainers or other interested parties are requested to
>   adapt their boards within the current merge window. All boards that
>   have not been fixed within the first week of the merge window are
>   considered unmaintained and without interest to the community and
>   will be removed.

 It's funny how this reminds me of package build failures in Debian; in
 such cases, we start by publishing the list of affected packages
 ideally with links to build logs and the name of corresponding
 maintainers.  After a while, we actually start Cc:ing the maintainers
 or filing bug reports against each failing package.

 Would it make sense to publish such a list of broken boards and
 corresponding maintainers?  (Maybe some makeall + scripts magic?)

 This is a sample list of Debian packages not declaring the upstream
 "Homepage" properly:
    http://lists.debian.org/debian-devel/2011/02/msg00367.html

-- 
Lo?c Minier

  reply	other threads:[~2011-06-28 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 10:55 [U-Boot] [STATUS] v2011.06 release, Merge Window is OPEN Wolfgang Denk
2011-06-28 15:24 ` Loïc Minier [this message]
2011-06-28 18:21   ` Wolfgang Denk
2011-06-29 18:37 ` Albert ARIBAUD
     [not found] <F766E4F80769BD478052FB6533FA745D19FAF4FE40@SC-VEXCH4.marvell.com>
2011-06-30 11:00 ` 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=20110628152416.GC31789@bee.dooz.org \
    --to=lool@dooz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox