linux-kernel - Re: linux-next: clean up time (pass 1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTim6MbS1E=9LyX=rsDr+JNuojPC4GQ@mail.gmail.com>
Date:	Thu, 2 Jun 2011 02:26:07 +0100
From:	Phillip Lougher <phillip.lougher@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: clean up time (pass 1)

On Wed, Jun 1, 2011 at 2:06 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 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

This is a surprise ... I'm sure I had commits in my squashfs
linux-next tree at the opening of the last but one merge window...

Linux 2.6.38 released 14 Mar 2011

$ git log --pretty="%ci %s"
...
2011-02-28 18:43:48 +0000 Squashfs: wrap squashfs_mount() definition
2011-02-28 18:35:44 +0000 Squashfs: xz_wrapper doesn't need to include squashfs_
2011-02-28 18:35:36 +0000 Squashfs: Update documentation to include compression
2011-02-28 18:35:28 +0000 Squashfs: Update Kconfig help text to include xz compr
2011-02-28 18:34:24 +0000 Squashfs: add compression options support to xz decomp
2011-02-28 18:21:59 +0000 Squashfs: extend decompressor framework to handle comp
2011-02-07 16:03:55 -0800 Linux 2.6.38-rc4

Phillip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/