Yin and Christopher, Thanks for the comments. We will revise this patch and also look at breaking it up, and then resubmit.
-David Coakley / AMD Open Source Compiler Engineering 2011/5/18 Christopher Bergström <cbergst...@pathscale.com>: > > > On Wed, May 18, 2011 at 9:17 PM, Yin Ma <y...@absoft.com> wrote: >> >> >> 2. If redesign is difficult, please use /* bug xxxx*/ or other similar >> ways >> to comment all locations >> where will be changed before merging into the trunk. Currently, AMD >> usually doesn't >> add any #ifdef or /* bug xxxx*/ like what Pathscale did before, which >> makes people difficult >> to track all changes associated to a certain problem. Since these >> changes are in mulitple >> components, it is better to add it. >> > With modern version control systems this shouldn't be an issue at all. The > problem I see and I wish would come to a complete stop is commits which > intermix issues. Maybe someone on OSG can propose this to be part of the > commit process.. ? > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
