Release 3.10: Backports (reminder and action needed)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

As we have branched release 3.10 (some time ago), patches that are being backported to 3.8/9 and are *applicable* to 3.10 need to be backported to 3.10 as well.

An analysis of this state since branching shows the following commits in 3.9 not backported to 3.10. Ashish, request you to address this at your convenience.

bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a (Ashish Pandey) Wed, 11 Jan 2017 17:19:30 +0530 cluster/ec: Do not start heal on good file while IO is going on

0f63bda0df91ee7ff42e3262c74220178ef87a21 (Ashish Pandey) Thu, 19 Jan 2017 18:20:44 +0530 cluster/disperse: Do not log fop failed for lockless fops

Thanks,
Shyam
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux