linux-kernel - Re: [GIT PULL] core/printk changes for v3.1

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:	Tue, 26 Jul 2011 13:30:06 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnaud Lacombe <lacombar@...il.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	SergeySenozhatsky <sergey.senozhatsky@...il.com>,
	DaveJones <davej@...hat.com>
Subject: Re: [GIT PULL] core/printk changes for v3.1

On Tue, Jul 26, 2011 at 1:12 PM, Arnaud Lacombe <lacombar@...il.com> wrote:
>
> [0]: I still have to find an easy way to transfer patch between gmail
> and my tree... For now, I ruled out mutt as it mangle the patch...

The gmail web interface on the *receiving* end is easy enough, and I
do it all the time: just go to the per-email menu in the upper right
corner of the email, and choose "Show original". Then you just save
that, and you're done.

Sadly, the gmail web interface cannot *send* patches without
whitespace-mangling them. You have to send them as attachements, and
there is no way to say "do this attachement inline".

Sad, sad, sad. gmail gets so many other things right, but sending
patches is a big pain in the *ss for no good reason.

The gmail web client also does threading the wrong way (by subject
line rather than by following references), but that's apparently what
Windows people want and are used to because of how Exchange works. Or
so I've been told - I've never touched that pile of crap. It's sad how
it has then resulted in crud in gmail. It's not like proper threading
is some kind of unheard-of feature..

                   Linus
--
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/