From: Stephen Rothwell <sfr@canb•auug.org.au>
To: linux-next@vger•kernel.org
Cc: LKML <linux-kernel@vger•kernel.org>
Subject: linux-next: clean up time (pass 1)
Date: Wed, 1 Jun 2011 11:06:16 +1000 [thread overview]
Message-ID: <20110601110616.861247de.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi all,
Looking through the trees currently included in linux-next, I get the
feeling that some of them may be obsolete.
Here is a list of tree that had no commits in them at the openning of the
previous two merge windows:
linux-spec
pxa
galak
ceph
configfs
jfs
squashfs
vfs-scale
kconfig
ide
powertools
swiotlb
input-mt
lsm
embedded
firmware
backlight
uclinux
hdlc
lblnet
bdev
cputime
jc_docs
nommu
audit
irda
i7300_edac
gpio
xen
sfi
asm-generic
hwpoison
sysctl
slabh
scsi-post-merge
I have no problem with including trees that are only used now and then,
but if any of the above have fullfilled their need, please let me know
and I will remove them. (In some cases being in the above list may just
mean that the proicess is not working very well and things are not being
included in linux-next before the merge window opens.)
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-06-01 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 1:06 Stephen Rothwell [this message]
2011-06-01 1:12 ` linux-next: clean up time (pass 1) Tejun Heo
2011-06-01 1:25 ` Stephen Rothwell
2011-06-02 1:26 ` Phillip Lougher
2011-06-02 1:38 ` Stephen Rothwell
2011-06-02 2:25 ` Phillip Lougher
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=20110601110616.861247de.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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