Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932627AbYF3SWx (ORCPT ); Mon, 30 Jun 2008 14:22:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932291AbYF3SWc (ORCPT ); Mon, 30 Jun 2008 14:22:32 -0400 Received: from main.gmane.org ([80.91.229.2]:41744 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932442AbYF3SWb (ORCPT ); Mon, 30 Jun 2008 14:22:31 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Kari Hurtta Subject: Re: [PATCH 3/3] Fix copy_user on x86_64 Date: 30 Jun 2008 21:22:18 +0300 Message-ID: <5dlk0mdbqd.fsf@Hurtta06k.keh.iki.fi> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: cs130027.pp.htv.fi User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 29 Linus Torvalds 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/