On Tue, Sep 9, 2014 at 9:54 AM, Peter Senna Tschudin <peter.senna@xxxxxxxxx> wrote: > On Tue, Sep 9, 2014 at 3:45 PM, Greg Freemyer <greg.freemyer@xxxxxxxxx> wrote: >> >> >> On September 8, 2014 11:08:46 PM EDT, nick <xerofoify@xxxxxxxxx> wrote: >>>I am attaching a trial patch again , please let me known if there are >>>any issues for me to fix. >>>Nick >> >> Nick, I guess you know this list is a training ground for the main lists. As such the same rules are enforced when it comes to formatting. >> >> Patches as an attachment are simply not acceptable. You have to do them inline. I'm surprised people are even opening your attachments to look at them. > > My understanding is that the problem is not with attachments, but with > using strange things like base64 for attachments. Nick has used plain > text attachment which seem perfectly fine for me. Check this: > > http://www.tux.org/lkml/ > > "If I get a patch in an attachment (other than a "Text/PLAIN" type > attachment with no mangling and that pretty much all mail readers and > all tools will see as a normal body), I simply WILL NOT apply it unless > I have strong reason to. I usually wont even bother looking at it, > unless I expected something special from the sender. > > Really. Don't send patches as attachments. > > Linus" > > So plain text attachment seem to be acceptable... > > >> >> Greg >> -- >> Sent from my Android phone with K-9 Mail. Please excuse my brevity. >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies@xxxxxxxxxxxxxxxxx >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > > > -- > Peter I understand that , sorry Guys. I am going to fix this later including my spell checks. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
