Re: 3.7 bugs need a clone from mainline?

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

 





On 04/29/2015 11:55 AM, Atin Mukherjee wrote:
I've seen few cases where we are using mainline bugs in submitting
patches in 3.7 release. Process wise this looks incorrect to me. IIRC,
earlier the smoke used to complaint about it, but I am not seeing that
either these days. Any recent changes on this?

IMO, we should clone all the mainline bugs which are been fixed for 3.7
and associate 3.7 tracker bugs on them instead of having them in
mainline bugs. Thoughts?
Yes, this is the recommended procedure. Niels had reminded us [1] of this some time back..
-Ravi
[1] http://www.gluster.org/pipermail/gluster-devel/2014-June/041232.html
~Atin
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.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