On Tue, Sep 10, 2013 at 2:13 PM, Paul Barker <p...@paulbarker.me.uk> wrote: > On 10 September 2013 13:06, Hans Beckérus <hans.becke...@gmail.com> wrote: >> On Tue, Sep 10, 2013 at 2:00 PM, Paul Barker <p...@paulbarker.me.uk> wrote: >>> On 10 September 2013 12:44, Hans Beckérus <hans.becke...@gmail.com> wrote: >>>> Could someone please verify if this patch (original v3 post) can be >>>> saved without line-feed corruption? It seems very client dependent how >>>> a message is saved, irrespective of source format. Some client seems >>>> to cut lines like crazy, others does not. >>>> >>>> Thanks. >>>> Hans >>>> >>> >>> Looking at "Show Original" in gmail still shows this to be garbled. >>> Perhaps save it as a .patch file and attach that to an email? That >>> should prevent any mail client from touching it. >>> >> Oh. But hang on here. Is it allowed to commit patches in the form of >> an attachment? >> Then why are we at all messing with the formatting and using git >> send-email to avoid white-spaces etc? >> If attachments are allowed then that will definitely save me some work ;) >> > > Ok, I've looked again and > http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded > doesn't mention attached patches as allowed. This is what the -contrib > repos were created for, perhaps you could request access to > http://git.openembedded.org/openembedded-core-contrib/ and push a > branch there, then send a pull request. > Yes, or I will just try to find a simple stupid mail client that does not mess up the formatting. I will try later today from a different client. That will be the last attempt. I am making a complete fool out of myself already ;)
Thanks. Hans > -- > Paul Barker > > Email: p...@paulbarker.me.uk > http://www.paulbarker.me.uk _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
