On Tuesday, 6 March 2018 6:30:25 AM NZDT Burton, Ross wrote: > I was about to write a long email explaining all this but my dinner is > almost ready. > > Short version: patch fuzz is dangerous, we've had patches apply using fuzz > which actually break the code, or doing something else stupid like repeat a > statement. > > We'd like to eventually have do_patch rejecting any fuzz on these grounds, > so I wrote a nasty script to rebase all the patches and am reviewing them > bit by bit. Note that two of these patches are deleting patches that we've > been applying although upstream have already applied the same fix...
So, for the purposes of being able to know this looking back in the git history can you please put this in the commit message? Fine if every single one is a copy-paste, but it shouldn't be blank particularly if someone's asking now. Thanks, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
