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

[Arnaud Lacombe]

Hi,

On Tue, Jul 26, 2011 at 4:30 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Tue, Jul 26, 2011 at 1:12 PM, Arnaud Lacombe <lacombar@xxxxxxxxx> 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.
>
yes and no. This works locally, but my desktop machine, and my dev
machine are not the same, so I have to do an extra-copy. Moreover,
this gets complicated when working remotely.

I guess the solution I'll ends-up doing is a mix between tagging the
mail in gmail, and retrieving the mbox/maildir through IMAP, but I'd
need a way to tag a single message, not a conversation...

> 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..
>
agree on most of that :)

It would have been nice if there was a Labs feature to provide
threading the traditional way and to provide a way for inline
attachment. If some people at Google read this message... who knows!

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