From: Matt Porter <mporter@kernel.crashing.org>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
Kumar Gala <galak@freescale.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 00/14] ppc32: Remove board ports that are no longer maintained
Date: Wed, 27 Jul 2005 10:15:03 -0700 [thread overview]
Message-ID: <20050727101502.B1114@cox.net> (raw)
In-Reply-To: <20050727162741.GC28681@gate.ebshome.net>; from ebs@ebshome.net on Wed, Jul 27, 2005 at 09:27:41AM -0700
On Wed, Jul 27, 2005 at 09:27:41AM -0700, Eugene Surovegin wrote:
> On Wed, Jul 27, 2005 at 12:13:23PM -0400, Michael Richardson wrote:
> > Kumar, I thought that we had some volunteers to take care of some of
> > those. I know that I still care about ep405, and I'm willing to maintain
> > the code.
>
> Well, it has been almost two months since Kumar asked about maintenance
> for this board. Nothing happened since then.
>
> Why is it not fixed yet? Please, send a patch which fixes it. This is
> the _best_ way to keep this board in the tree, not some empty
> maintenance _promises_.
When we recover our history from the linuxppc-2.4/2.5 trees we can
show exactly how long it's been since anybody touched ep405.
Quick googling shows that it's been almost 2 years since the last
mention of ep405 (exluding removal discussions) on linuxppc-embedded.
Last ep405-related commits are more than 2 years ago.
-Matt
next prev parent reply other threads:[~2005-07-27 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 15:32 [PATCH 00/14] ppc32: Remove board ports that are no longer maintained Kumar Gala
2005-07-27 16:13 ` Michael Richardson
2005-07-27 16:27 ` Eugene Surovegin
2005-07-27 17:15 ` Matt Porter [this message]
2005-07-27 23:34 ` Kumar Gala
2005-07-29 16:33 ` Michael Richardson
2005-07-29 17:03 ` Esben Nielsen
2005-07-29 18:10 ` Kumar Gala
2005-07-27 19:57 ` Andrew Morton
2005-07-27 23:35 ` Kumar Gala
2005-07-31 16:39 ` Kumar Gala
2005-08-30 1:46 ` Kumar Gala
2005-08-30 7:44 ` Eugene Surovegin
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=20050727101502.B1114@cox.net \
--to=mporter@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=galak@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mcr@sandelman.ottawa.on.ca \
/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;
as well as URLs for NNTP newsgroup(s).