On Sun, 7 Dec 2014, Luca Barbato wrote:
Soon I'll start sending some chunks of security fixes (since Google kindly provided me another batch of samples exercising faulty code) and I will need to clean the code I'm reading, I hope you'd not force me to redo 200+ patches or have me drop patches cleaning code that I have to read to track where the actual problem is.
Umm, why do security patches on top of cosmetics/reindentation anyway? Since they are security patches, they are supposed to get cherrypicked into releases anyway, right? And then you'd have to do the same conflict resolving as if you'd remove the cosmetics from your patchset anyway. Or, I really hope you aren't suggesting that we should cherrypick the cosmetics to the release branches along with the security fixes?
// Martin _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
