From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: old trees
Date: Fri, 20 Sep 2013 14:35:17 -0400 [thread overview]
Message-ID: <20130920183517.GH5707@phenom.dumpdata.com> (raw)
In-Reply-To: <20130917170124.0afa2e103a9977355ad7c72c@canb.auug.org.au>
On Tue, Sep 17, 2013 at 05:01:24PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> This message is bcc'd to each of the contacts for the trees listed below,
> so apologies if you get two copies.
>
> I have been inspired to check the ages of the trees included in
> linux-next. Below I have listed all the trees that have not been
> commited to in the past 6 months. Please let me know if the tree is not
> longer in use. I don't mind keeping these trees in linux-next if they
> will have continued use, but would like to remove any that are no longer
> needed.
Thank you for the prunning effort.
> ibft 1 year, 9 months ago
Can go away.
> swiotlb 11 months ago
Need it. Don't remove it pls.
> tmem 11 months ago
Can go away.
next prev parent reply other threads:[~2013-09-20 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:01 linux-next: old trees Stephen Rothwell
2013-09-17 11:14 ` Sekhar Nori
2013-09-17 23:09 ` Stephen Rothwell
2013-09-17 12:53 ` Josh Boyer
2013-09-17 23:11 ` Stephen Rothwell
2013-09-17 15:36 ` Arnd Bergmann
2013-09-20 18:35 ` Konrad Rzeszutek Wilk [this message]
2013-09-23 0:02 ` Stephen Rothwell
2013-09-25 13:27 ` Jonathan Corbet
2013-09-25 23:46 ` Stephen Rothwell
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=20130920183517.GH5707@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).