From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH] fs/inode.c: include "internal.h" for external definitions Date: Mon, 17 Jan 2011 07:20:02 +0000 Message-ID: <20110117072002.GH22723@ZenIV.linux.org.uk> References: <0D753D10438DA54287A00B027084269764CE0E54E1@AUSP01VMBX24.collaborationhost.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" To: H Hartley Sweeten Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:40067 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752085Ab1AQHUE (ORCPT ); Mon, 17 Jan 2011 02:20:04 -0500 Content-Disposition: inline In-Reply-To: <0D753D10438DA54287A00B027084269764CE0E54E1@AUSP01VMBX24.collaborationhost.net> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Jan 11, 2011 at 06:21:59PM -0600, H Hartley Sweeten wrote: [snip] Fix your MUA, please. What you've somehow managed to produce was Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 and git-am is not happy with it, to put it mildly. I can work around that (view as attachment in mutt, save that, etc.) and if that had been anything more inspiring I'd bothered to undo the wreckage, apply by hand and recall how to tell git commit who's the author, but... Why had your MUA done that, anyway? I don't see anything in the text that might have possibly warranted something that weird... Al "tempted to reply with Content-Transfer-Encoding: morse" Viro