Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262018AbVEEKG7 (ORCPT ); Thu, 5 May 2005 06:06:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262022AbVEEKG7 (ORCPT ); Thu, 5 May 2005 06:06:59 -0400 Received: from khc.piap.pl ([195.187.100.11]:28676 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S262018AbVEEKG6 (ORCPT ); Thu, 5 May 2005 06:06:58 -0400 To: Rik van Riel Cc: Dave Hansen , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy References: <20050504170156.87F67CE5@kernel.beaverton.ibm.com> From: Krzysztof Halasa Date: Thu, 05 May 2005 12:06:55 +0200 In-Reply-To: (Rik van Riel's message of "Wed, 4 May 2005 21:09:49 -0400 (EDT)") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 596 Lines: 15 Rik van Riel writes: > The problem is replying to an attachment. The reason why having > the patch in the main mail body is good is that it gets quoted > by the email software and you can easily reply to individual > parts of the patch. If the attachment is "disposition=inline", does the problem still exist? -- Krzysztof Halasa - 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/