From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933184Ab3CTQ4U (ORCPT ); Wed, 20 Mar 2013 12:56:20 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:56036 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754361Ab3CTQ4T (ORCPT ); Wed, 20 Mar 2013 12:56:19 -0400 Message-ID: <5149EA30.8020302@wwwdotorg.org> Date: Wed, 20 Mar 2013 10:56:16 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Mark Brown CC: Laxman Dewangan , "linux-kernel@vger.kernel.org" , Stephen Warren , "linux-tegra@vger.kernel.org" , "lrg@ti.com" Subject: Re: [PATCH 2/2] regulator: palmas: add input supply names References: <1363598989-25112-1-git-send-email-ldewangan@nvidia.com> <20130320123128.GM28775@opensource.wolfsonmicro.com> <5149B19E.90400@nvidia.com> <5149DEB5.7000709@wwwdotorg.org> <20130320163833.GT28775@opensource.wolfsonmicro.com> <5149E6F2.5070205@wwwdotorg.org> <20130320165227.GU28775@opensource.wolfsonmicro.com> In-Reply-To: <20130320165227.GU28775@opensource.wolfsonmicro.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/20/2013 10:52 AM, Mark Brown wrote: > On Wed, Mar 20, 2013 at 10:42:26AM -0600, Stephen Warren wrote: >> On 03/20/2013 10:38 AM, Mark Brown wrote: >>> On Wed, Mar 20, 2013 at 10:07:17AM -0600, Stephen Warren >>> wrote: >>>> On 03/20/2013 06:54 AM, Laxman Dewangan wrote: > >>>>> I generally send a patches on single git-send command git >>>>> send-emal --to=ldewangan@nvidia.com 0000.patch 0001.patch > >>>> Don't do that; send *.patch. If you don't, then patches 2..n >>>> don't end up being "in-reply-to" patch 1, so they won't show >>>> up as a single email thread. > >>> The two should be equivalent (though the glob is much easier >>> to type)? The result of the globbing ought to be what Laxman is >>> typing by hand assuming that he's getting the order correct. > >> If you send *.patch at once, git send-email adds an in-reply-to >> header to the email which sets up the threading. If you send the >> patches 1-by-1, this header isn't added, since git send-email >> doesn't have a clue what message ID it chose for patch 1. Unless >> you pass the --in-reply-to command-line option, that is. > > Indeed - I think you may have quoted the wrong bit of Laxman's > mail there? The bit you're replying to is doing it as a single > command, though he did talk about doing this in multiple commands > elsewhere in his mail. Oh right yes. I'd seen 0000.patch and not that there were multiple entries in the command-line that listed (I assume) all the files. Sorry for the noise.