> With Infernalis Ceph move to c++11 (and CMake), we will see more conflicts when backporting bug fixes to Hammer. Good point, Loic! > Any ideas you may have to better deal with this would be most welcome. A couple thoughts pop into mind. When I joined the project, I was told that doing backports is a good way to get into the codebase, and after some months I can confirm that this is true. Loic has literally bent over backwards to help me along the way, and thanks to that I have made some progress. Still, the factor determining whether a backport is trivial or non-trivial is often my own "cluenessness". I would suggest to developers that they keep backporting in the back of their mind as they design and implement bugfixes. Will the backport be doable even by a relatively inexperienced backporter? Is there a way to make it easier on the backporter? I would suggest that it is in the developers' best interest to make a little extra effort in this direction, as it will reduce the probability of the backporter asking them for help later ;-) Regards -- Nathan Cutler Software Engineer Distributed Storage SUSE LINUX, s.r.o. Tel.: +420 284 084 037 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
