On Sat, Aug 09, 2014 at 05:01:24PM +0000, Duncan wrote:
> Jose Ildefonso Camargo Tolosa posted on Sat, 09 Aug 2014 11:06:37 -0500 as
> excerpted:
>
> > 3.16 (still in development)
>
> ??
>
> 3.16 has been out for nearly a week now and we're nearing half-way thru
> the 3.17 commit-window. Based on the kernel git I have here, Linus'
> commit officially changing the makefile entry to 3.16 was on Sunday, Aug
> 3, at 15:25:02 -0700.
>
> The last pre-3.16 commit was a merge of two timer-related fixes from the
> tip-tree at 9:58:20 -0700 that morning.
>
> So where does your "still in development" come from?
You could argue that since 3.16.0 does not have the recently found
deadlock patch that's been plaging 15 and 16 (14 not as much for me),
it's not usable for some (it ran about 1 day on my laptop before
deadlocking, and maybe an hour at most on my server).
I sure hope that deadlock patch is going to be added to the 3.16.x tree,
I'm not super stocked with being stuck at 3.14.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
