From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Henningsson Subject: Patch submission process (was: [PATCH] Add "Line In" input jack constants) Date: Thu, 06 Oct 2011 08:46:22 +0200 Message-ID: <4E8D4EBE.6030703@canonical.com> References: <4E8C6332.2080902@canonical.com> <20111005150753.GB13377@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by alsa0.perex.cz (Postfix) with ESMTP id 78BAC103A3B for ; Thu, 6 Oct 2011 08:46:26 +0200 (CEST) In-Reply-To: <20111005150753.GB13377@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: Takashi Iwai , ALSA Development Mailing List List-Id: alsa-devel@alsa-project.org On 10/05/2011 05:07 PM, Mark Brown wrote: > but please follow the patch submission process in SubmittingPatches - in > particular, don't send your patch as an attachment. I find this hard to fulfil at times, in particular when I want to add something to the email that I don't want to be a part of the commit message. Is this possible with git send-email, and without sending the patch as an attachment? -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic