From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [RFC PATCH] telephony: Move to staging
Date: Mon, 30 Jan 2012 14:18:38 -0800 [thread overview]
Message-ID: <20120130221838.GA5904@suse.de> (raw)
In-Reply-To: <cd8d3ef8b646dc0b1c451e61c57d639cadbc7c21.1327961290.git.joe@perches.com>
On Mon, Jan 30, 2012 at 02:11:34PM -0800, Joe Perches wrote:
> This stuff is really old and in quite poor shape.
> Does anyone still use it?
>
> If not, I think it's appropriate to let it simmer
> in staging for a few releases.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Is this really unmaintained?
Fine with me, but you need a message/TODO file that says if someone
needs/wants it, to ask you, and it will be moved back.
Care to add that to the patch and resend it?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-30 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 22:11 [RFC PATCH] telephony: Move to staging Joe Perches
2012-01-30 22:18 ` Greg KH [this message]
2012-01-30 22:28 ` Joe Perches
2012-01-30 22:54 ` [RFC PATCH V2] " Joe Perches
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=20120130221838.GA5904@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).