From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: linux-next: old trees
Date: Tue, 17 Sep 2013 17:01:24 +1000 [thread overview]
Message-ID: <20130917170124.0afa2e103a9977355ad7c72c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
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.
Tree Last commit
---- -----------
4xx 1 year, 4 months ago
apm 1 year, 5 months ago
asm-generic 9 months ago
audit 1 year, 8 months ago
audit-current 1 year, 8 months ago
configfs 1 year, 10 months ago
cpupowerutils 1 year, 7 months ago
cputime 1 year, 9 months ago
davinci 2 years, 2 months ago
dwmw2 6 months ago
dwmw2-iommu 9 months ago
embedded 5 years ago
firmware 4 years, 4 months ago
fsnotify 9 months ago
fw-nohz 10 months ago
hsi 1 year, 8 months ago
hwpoison 2 years, 11 months ago
hwspinlock 2 years ago
ibft 1 year, 9 months ago
isci 1 year, 2 months ago
ixp4xx 7 months ago
jc_docs 2 years, 6 months ago
kconfig 12 months ago
kgdb 7 months ago
logfs 10 months ago
lzo-update 7 months ago
ocfs2 1 year, 1 month ago
omfs 1 year, 11 months ago
openrisc 6 months ago
osd 9 months ago
parisc 8 months ago
pcmcia 1 year, 7 months ago
pstore 6 months ago
random 7 months ago
sh 7 months ago
sh-current 1 year, 2 months ago
swiotlb 11 months ago
sysctl 1 year, 6 months ago
tmem 11 months ago
uclinux 7 months ago
unicore32 10 months ago
uprobes 1 year, 6 months ago
viafb 1 year, 6 months ago
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-09-17 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:01 Stephen Rothwell [this message]
2013-09-17 11:14 ` linux-next: old trees 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
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=20130917170124.0afa2e103a9977355ad7c72c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).