On 23/09/12 23:14, Lucas De Marchi wrote: > It sounds like an excuse to not do the right thing. The manual > intervention should be very minimal and it shouldn't be a source of > bugs... once it compiles, it should work as if the paths haven't > changed.
It's easier to mis-merge, and that's a source of bugs. Everything that is not completely automatic is a potential source of bugs. The word "should" is responsible for 87% of all software bugs, so I don't really trust that. With that being said, I do trust you, and you said that svn-git-am can handle it gracefully, lets just hope it does. I'm fine with waiting with applying the patches, but lets have a schedule for that. What's the plan for this merge? When will I be able to merge stuff? And btw, do we make sure history is correctly kept for source files? Cause that can be crazily annoying. -- Tom. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
