On Fri, 31 Aug 2012 10:37:40 +0800 Alex Wu <zhiwen...@linux.intel.com> said:
> Hi, > Due to some legacy applications use elm_entry_magnifier_disabled_set(), > add the fake function in order to be backward-compatible. ok. here comes the rub. elm never had such an api. this was a custom fork done without review from upstream (the open source side). from that point of view we can only reject such a patch. sorry. any app using such an api should be modified or the project (tizen in this case) needs to carry the patch "forever". this is the price of making a fork then continuing that fork in private and making everything depend on it and never pushing your work back upstream. thought i'd like to be nice and say yes, this is a lesson that must be learned and thus this is a "no". this is nothing new in the linux world. many a kernel, glibc, xorg, gtk, etc. patch has been rejected and needed re-doing and anything depending on that patch would have needed adjustment too. the solution is to push early, push often. :) let upstream know what you are doing AS you do it. until it's approved and "in" don't depend on it. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
