On 2013-01-31 15:20, Greg Kroah-Hartman wrote:
On Thu, Jan 31, 2013 at 04:55:26PM +0200, Aaro Koskinen wrote:
Hi,
On Thu, Jan 31, 2013 at 01:28:31PM +0000, Ian Abbott wrote:
On 2013-01-31 13:06, Greg Kroah-Hartman wrote:
On Thu, Jan 31, 2013 at 11:45:15AM +0000, Ian Abbott wrote:
That wasn't really the problem I was having, as I'd already given up
by the second patch. The problem was that all the tabs in the first
two patches had been expanded to spaces. The remaining 8 patches
never had that problem!
[...]
Perhaps something on your end is messing these up?
It seems that way since the copies in <http://driverdev.linuxdriverproject.org/pipermail/devel/2013-January.txt.gz>
are fine. It's strange that only those two patches were affected,
and in all three copies!
I am receiving the patches through a Microsoft Exchange server
though, and it does do strange things like re-encode all emails that
pass through it. (I bypass that server when sending patches to
prevent them all getting re-encoded as MIME quoted-printable.)
Tab to space conversion is a known bug in Exchange Server. See:
http://support.microsoft.com/kb/945870
We're up to Update Rollup 10 for Exchange 2007 Service Pack 1, so I
don't think we should be experiencing that bug. Besides, most patches
come through okay (except for the re-encoding to quoted-printable part,
but that's not really a problem).
I recall it did other kind of random mangling to Linux patches as well,
better just avoid it.
Agreed. I do avoid it when posting patches.
Latest versions of Exchange do have an option to not mangle the body of
the emails so that patches will come through properly.
Talk to your admin to turn that on if you can.
That's good to know, although I'm stuck with Exchange 2007 here for now.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@xxxxxxxxx> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
