All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot v2010.12 released - Merge Window OPEN
Date: Wed, 26 Jan 2011 01:15:27 +0100	[thread overview]
Message-ID: <4D3F679F.6060406@ahsoftware.de> (raw)
In-Reply-To: <20110125201716.BEB94B187@gemini.denx.de>

Am 25.01.2011 21:17, schrieb Wolfgang Denk:
> Dear Alexander Holler,
>
> In message<4D3E8855.4070003@ahsoftware.de>  you wrote:
>>
>>>      *****************************************************************
>>>      * Currently,>100 ARM boards are *broken* and *do not compile*. *
>>>      *****************************************************************
>>>
>>>      Board maintainers or othe rinterested parties are requested to
>>>      adapt their boards to the new code in the timeframe of the
>>>      upcoming release v2010.03; all boards that have not been converted
>>>      by then, i. e. that are still broken then, are considered
>>>      unmaintained and without interest to the community and will be
>>>      removed.
>>
>> Maybe just a
>>
>> #error Code for this board doesn't compile since at least #date#
>>
>> or a similiar message in foo_config.h would be a way to inform people
>> early that the code needs some work.
>>
>> This way the source for the board could be visible for some more time in
>> the repository.
>
> Patches welcome...

I don't have a script or similiar which tests which boards does compile, 
but adding a

if fail then echo "#error $board doesn't compile since $(date)" 
 >>include/configs/board.h

to such a script should do the trick.

I think this will cost less time than removing these boards (with the 
next release) and will give people more time to implement the necessary 
changes. When those sources get removed, it will be more work to get 
them in back, therefore I would prefer to leave such boards in the repo 
for some more time.

A sideeffect of such an #error would be, that there would be an 
indication about how long a board doesn't compile.

Regards,

Alexander

  reply	other threads:[~2011-01-26  0:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 20:15 [U-Boot] U-Boot v2010.12 released - Merge Window OPEN Wolfgang Denk
2010-12-23 10:18 ` Andreas Bießmann
2011-01-25  8:22 ` Alexander Holler
2011-01-25 20:17   ` Wolfgang Denk
2011-01-26  0:15     ` Alexander Holler [this message]
2011-01-26  7:38       ` Wolfgang Denk
2011-01-26  8:17         ` Alexander Holler
2011-01-26  8:36           ` Stefano Babic
2011-01-26  9:39             ` Wolfgang Denk
2011-01-28 10:34               ` Alexander Holler
2011-01-28 13:17                 ` Stefano Babic
2011-01-26  9:19           ` Wolfgang Denk
2011-01-26  9:27             ` Alexander Holler

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=4D3F679F.6060406@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --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.