Gmail and flowed text (was Re: Correction to LZO1X)

[Satyam Sharma]

[ off the original topic, Cc: list trimmed ]

On 7/11/07, Nitin Gupta <nitingupta910@xxxxxxxxx> wrote:
> [...]
>  #define LZO1X_MEM_COMPRESS     (16384 * sizeof(unsigned char *))
>  #define LZO1X_1_MEM_COMPRESS   LZO1X_MEM_COMPRESS
>
> -#define lzo1x_worst_compress(x) (x + (x / 64) + 16 + 3)
> +#define lzo1x_worst_compress(x) ((x) + ((x) / 16) + 64 + 3)
>
>  /* This requires 'workmem' of size LZO1X_1_MEM_COMPRESS */
>  int lzo1x_1_compress(const unsigned char *src, size_t src_len,

And yet another patch falls victim to format=flowed ...

I need some ideas here myself:

I don't want to subscribe from my university mail account -- I like
to keep important messages on server, and the account has a
100 MB or so limit that wouldn't survive a week of lkml traffic.

Which leaves Gmail, but Gmail has the flowed text disease (that
cannot be disabled) and although Gmail offers SMTP/POP, our evil
proxy/NAT setup here wouldn't let me make any use of it to access
it from some other MUA such as pine/mutt.

I use Paul Jackson's wonderful "sendpatchset" script (when sending
patches that start new threads), but it's frustrating not to be able to
reply to existing threads with patches from Gmail itself (from which I
have subscribed to lkml).

I suspect others must have come across this ... any suggestions?

Satyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/