public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Removal of doc/README.scrapyard
Date: Fri, 24 Oct 2014 21:31:24 +0200	[thread overview]
Message-ID: <20141024193124.0A9323830E9@gemini.denx.de> (raw)
In-Reply-To: <201410241709.09895.marex@denx.de>

Dear Marek,

In message <201410241709.09895.marex@denx.de> you wrote:
> 
> I've recently been removing support for some boards and this README.scrapyard 
> file came up again. The file is supposed to be used to keep track of removed 
> boards.

Or, to put it differently, to document what was once suported and now
is no longer.

> I wonder if we shouldn't get rid of this README.scrapyard. Personally,
> I don't find much value in it ; if I am looking for some ancient board,
> I just do git log -p and search for whatever I need.

Well, of course you can search - but the you need to know what to
dearch for.  If you have no idea what to look for, then a text file
listing all the options that onces existed might be helpful to focus
your search - say, on specific board names and such.

That was the idea behind README.scrapyard - give you information what
you could use as search anchors for closer investigations.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It may be bad manners to talk with your mouth full, but it isn't  too
good either if you speak when your head is empty.

  reply	other threads:[~2014-10-24 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 15:09 [U-Boot] [RFC] Removal of doc/README.scrapyard Marek Vasut
2014-10-24 19:31 ` Wolfgang Denk [this message]
2014-10-24 22:28   ` Simon Glass

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=20141024193124.0A9323830E9@gemini.denx.de \
    --to=wd@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox