From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] logodl: : remove code for yet another corpse
Date: Wed, 06 Oct 2010 19:09:06 +1100 [thread overview]
Message-ID: <4CAC2EA2.5070408@gmail.com> (raw)
In-Reply-To: <4CAC0000.5050504@emk-elektronik.de>
On 06/10/10 15:50, Reinhard Meyer wrote:
> Dear Graeme Russ,
>> On Wed, Oct 6, 2010 at 2:32 PM, Marek Vasut<marek.vasut@gmail.com>
>> wrote:
>> The first thing that is always said when someone asks about a board they
>> have been given/bought with an old version of U-Boot is to upgrade,
>> pretty
>> hard to do if it's been nuked from the tree ;)
>
> A text file in doc, like README.historic-boards would suffice, indicating
> which u-boot release that board was nuked. It would also be good to mention
> CPU that board used. So anyone looking to support a similar board could
> have
> a look and with git its possible to get the old files.
>
Yeah, I think this is a good solution. Maybe mentioning the last known
maintainer / major code contributor would also be helpful
Regards,
Graeme
next prev parent reply other threads:[~2010-10-06 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 20:03 [U-Boot] [PATCH] logodl: : remove code for yet another corpse Wolfgang Denk
2010-10-06 3:32 ` Marek Vasut
2010-10-06 3:41 ` Graeme Russ
2010-10-06 4:48 ` Marek Vasut
2010-10-06 4:50 ` Reinhard Meyer
2010-10-06 8:09 ` Graeme Russ [this message]
2010-10-19 19:50 ` [U-Boot] [PATCH] doc/README.scrapyard: add documentation for abandoned boards Wolfgang Denk
2010-10-19 20:26 ` Wolfgang Denk
2010-10-19 19:50 ` [U-Boot] [PATCH] logodl: : remove code for yet another corpse Wolfgang Denk
2010-10-06 7:28 ` Wolfgang Denk
2010-10-18 19:49 ` 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=4CAC2EA2.5070408@gmail.com \
--to=graeme.russ@gmail.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