On Fri 11 May 2007 18:37, Wolfgang Denk pondered:
Dear Robin,
How would you like to handle patches like this?
Well, of course we reject such a patch, as it does not apply to any code after being linewrapped by a broken / misconfigured mailer.
I saw my mailer mangled it, but I didn't notice it was because Aubrey's was messed up first. I guess that is the fun of sending patches via a web interface like gmail... :)
Aubrey - can you resend via a mailer that will not mangle the longer lines on Monday? Thx.
[But I guess this was not exactly your question :-) ]
Should an arch maintainer put it in their git tree, and push you the change - (even though it is common code) or is a patch to the mailing list the best way to handle?
The "official" approach is that ALL patches get posted to the mailing list, from where the respective custodian will pick it up. I intend to be the "ragpicker" to collect all items that are left. At the moment this still suffers from a working patch tracking system, but this is in the works (I know, I promised this too often already).
No problem - I know that you/we all are busy, and everyone working all with the same rules makes things go faster...
Have a good weekend. -Robin