From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Removal of doc/README.scrapyard
Date: Fri, 24 Oct 2014 17:09:09 +0200 [thread overview]
Message-ID: <201410241709.09895.marex@denx.de> (raw)
Hello,
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.
The person removing a board is first supposed to fill in the blank fields in
this README.scrapyard , which are the upstream commit ID in which the board was
removed and the date at which the board was removed. Those two fields are known
only after the board removal patch was applied, thus those fields need to be
filled in later. This effectively means that the last removed board can have
those fields undefined for an extended period of time, until someone removes
another board and updates the README.scrapyard.
Only after updating README.scrapyard, one is supposed to add the board that was
removed into README.scrapyard, again with blank fields for the commit ID and
date of removal.
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.
What are your opinions on removing this file altogether ?
Best regards,
Marek Vasut
next reply other threads:[~2014-10-24 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 15:09 Marek Vasut [this message]
2014-10-24 19:31 ` [U-Boot] [RFC] Removal of doc/README.scrapyard Wolfgang Denk
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=201410241709.09895.marex@denx.de \
--to=marex@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