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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jul 2007 15:41:53 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Satyam Sharma" <satyam.sharma@...il.com>
Cc:	"Nitin Gupta" <nitingupta910@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Gmail and flowed text (was Re: Correction to LZO1X)

On 11/07/07, Satyam Sharma <satyam.sharma@...il.com> wrote:
> [ off the original topic, Cc: list trimmed ]
>
> On 7/11/07, Nitin Gupta <nitingupta910@...il.com> 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?
>

1) talk to the administrators and convince them to allow you to use
gmails SMTP/POP feature with a different MUA so you don't have to use
the web interface.

2) If you have a box available at home (or elsewhere), use that to
relay mail through.

3) Use attachments for patches (sucks, but you may have to).


-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/