Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: sjhill@realitydiluted.com
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Pete Popov <ppopov@embeddedalley.com>,
	"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: deletion of boards
Date: Tue, 13 Sep 2005 06:42:13 -0500 (CDT)	[thread overview]
Message-ID: <E1EF9Az-0004Si-Q4@real.realitydiluted.com> (raw)
In-Reply-To: <20050913122440.GA3224@linux-mips.org>

> > The AMD Pb1000, Pb1100, Pb1500, and Hydrogen3 boards are not up to date
> > in 2.6 and seem to be of very little interest to anyone. Any objections
> > if I remove them to reduce the clutter?
> 
> The inflation of evaluation boards is generally some sort of problem; in
> many cases they are on the market only for a very short time before they're
> replaced - we're talking about a time frame of like 6 months or so.  That
> means the time that a Linux port is actually of interest if often just
> as short.  Which means, we have quite a few candidates for deletion.
> 
I would agree with this. Could I make a small suggestion? How about for
boards that are going to be removed, someone at least tries to build a
kernel for it, if it works then tag CVS as such for that board. If not,
blow it away. This allows someone who possibly has an interest later on
to at least be able to pull the last known working snapshot for their
board. Just a thought.

-Steve

  reply	other threads:[~2005-09-13 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  1:30 deletion of boards Pete Popov
2005-09-13  7:14 ` Thomas Sailer
2005-09-13  7:22 ` Matej Kupljen
2005-09-13  7:26   ` Pete Popov
2005-09-13  7:35     ` Matej Kupljen
2005-09-13 15:57       ` Pete Popov
2005-09-13 12:24 ` Ralf Baechle
2005-09-13 11:42   ` sjhill [this message]
2005-09-13 19:35 ` Sylvain Munaut
2005-09-13 19:51   ` Pete Popov

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=E1EF9Az-0004Si-Q4@real.realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@embeddedalley.com \
    --cc=ralf@linux-mips.org \
    /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