From: Kari Hurtta <hurtta+gmane@siilo.fmi.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Fix copy_user on x86_64
Date: 30 Jun 2008 21:22:18 +0300 [thread overview]
Message-ID: <5dlk0mdbqd.fsf@Hurtta06k.keh.iki.fi> (raw)
In-Reply-To: <alpine.LFD.1.10.0806300835220.28533@hp.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Mon, 30 Jun 2008, Vitaly Mayatskikh wrote:
> >
> > "For this reason, all patches should be submitting e-mail "inline".
> > WARNING: Be wary of your editor's word-wrap corrupting your patch,
> > if you choose to cut-n-paste your patch."
> >
> > My first thought was "should be attached inline".
>
> Yeah, no, the "inline" there means literally as no attachment at all, but
> inline in the normal mail.
And not as own mime body part with
Content-Disposition: inline
?
( As you see "inline" have several meanings.
yes. Some mail readers treats only first body part as 'inline'
and other have 'attachments'.
)
/ Kari Hurtta
next prev parent reply other threads:[~2008-06-30 18:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 21:52 Vitaly Mayatskikh
2008-06-28 18:26 ` Linus Torvalds
2008-06-30 15:12 ` Vitaly Mayatskikh
2008-06-30 15:55 ` Linus Torvalds
2008-06-30 16:16 ` Andi Kleen
2008-06-30 18:22 ` Kari Hurtta [this message]
2008-07-02 13:48 ` [PATCH 1/2] Introduce copy_user_handle_tail routine Vitaly Mayatskikh
2008-07-02 14:06 ` Andi Kleen
2008-07-02 14:31 ` Vitaly Mayatskikh
2008-07-02 15:06 ` Andi Kleen
2008-07-02 15:32 ` Vitaly Mayatskikh
2008-07-02 15:40 ` Andi Kleen
2008-07-02 15:58 ` Vitaly Mayatskikh
2008-07-02 18:54 ` Andi Kleen
2008-07-03 2:35 ` Linus Torvalds
2008-07-07 12:09 ` Vitaly Mayatskikh
2008-07-07 12:12 ` Vitaly Mayatskikh
2008-07-07 16:43 ` Andi Kleen
2008-07-07 16:21 ` Linus Torvalds
2008-07-07 17:05 ` Vitaly Mayatskikh
2008-07-09 13:03 ` Ingo Molnar
2008-07-09 13:16 ` Vitaly Mayatskikh
2008-07-09 13:52 ` Ingo Molnar
2008-07-02 13:53 ` [PATCH 2/2] Fix copy_user on x86 Vitaly Mayatskikh
2008-07-02 14:08 ` Andi Kleen
2008-07-02 14:36 ` Vitaly Mayatskikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dlk0mdbqd.fsf@Hurtta06k.keh.iki.fi \
--to=hurtta+gmane@siilo.fmi.fi \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®