On Thu, Jun 2, 2011 at 2:38 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Phillip, > > On Thu, 2 Jun 2011 02:26:07 +0100 Phillip Lougher <phillip.lougher@xxxxxxxxx> wrote: >> >> > 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 > > plus or minus 1 day (and timezone jitter :-)): > > $ git rev-list --no-merges next/20110314/origin..next/20110314/squashfs | wc -l > 0 > $ git rev-list --no-merges next/20110315/origin..next/20110315/squashfs | wc -l > 0 > $ git rev-list --no-merges next/20110316/origin..next/20110316/squashfs | wc -l > 6 > Bugger, maybe I forgot to push, though I thought I did :-) Phillip > It doesn't really matter, it was just a quick metric to choose a subset > of trees to look at. > > -- > Cheers, > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx > http://www.canb.auug.org.au/~sfr/ > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
