Submit by mail

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Ellerman wrote:
> On 6/12/06, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
>> Inline patches are much more likely to be mangled (e.g. LF -> CRLF) than
>> attachments, so there is some risk to that approach.
> 
> Sure, but any decent mailer should be able to send mail without
> munging whitespace _if you tell it not to_. Having said that, it's
> probably best to try and make the bundle code as immune to whitespace
> changes as possible. Perhaps optionally, like patch's
> --ignore-whitespace.

It is a tall order make bundles produce reproducible results, be
verifiable, and to tolerate whitespace changes.  Not saying we can't,
but it's very hard.

One of the problems is that the line separator is not always constant--
some files mix LF and CRLF.  Another is that whitespace at the end of
lines is often eaten, or used to indicate a soft break in format=flowed
text.

> Inline patches are much easier to read and comment on, in some MUAs at
> least. And some communities won't accept patches any other way.

Sigh, it's frustrating to work around other peoples' workarounds...

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEjMZE0F+nu1YWqI0RArPaAJ0cCnvXzFgWt2eZ5UAhqo/ra2RUzwCfYzWl
Oshwm8du6tblLo07Z/gxHjI=
=WeY8
-----END PGP SIGNATURE-----