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 09:17:33 +0100	[thread overview]
Message-ID: <4D3FD89D.7000509@ahsoftware.de> (raw)
In-Reply-To: <20110126073801.11A43BB0B9@gemini.denx.de>

Hello,

Am 26.01.2011 08:38, schrieb Wolfgang Denk:

>> 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.
>
> Removing is simple, and the only proven way to clean up old mess.
> I see no reason to keep dead, unmaintained code in U-Boot for too
> long.

The question is the timeframe. I think when many of these boards will 
get removed with the next release, that's a bit short. Finding the stuff 
which doesn't work through the relocation is time consuming and people 
have to find the time to do this for older boards for which they 
currently don't actively develop. E.g for some of the boards under 
active development it has needed the last 3 month.

Regards,

Alexander

  reply	other threads:[~2011-01-26  8:17 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
2011-01-26  7:38       ` Wolfgang Denk
2011-01-26  8:17         ` Alexander Holler [this message]
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=4D3FD89D.7000509@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.