From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758819Ab2CITLF (ORCPT ); Fri, 9 Mar 2012 14:11:05 -0500 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:48592 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754746Ab2CITLD convert rfc822-to-8bit (ORCPT ); Fri, 9 Mar 2012 14:11:03 -0500 MIME-Version: 1.0 In-Reply-To: References: <1331018040-30725-1-git-send-email-yinghai@kernel.org> From: Bjorn Helgaas Date: Fri, 9 Mar 2012 12:10:32 -0700 Message-ID: Subject: Re: [PATCH 00/23] PCI, x86: pci root bus hotplug support To: Yinghai Lu Cc: Bjorn Helgaas , Jesse Barnes , x86 , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 9, 2012 at 11:55 AM, Yinghai Lu wrote: > On Fri, Mar 9, 2012 at 9:34 AM, Bjorn Helgaas wrote: >> On Fri, Mar 9, 2012 at 1:19 AM, Yinghai Lu wrote: >>> On Thu, Mar 8, 2012 at 4:43 PM, Bjorn Helgaas wrote: >> >>>> The notes about "-v2, -v3, -v4, etc." are not really useful in the >>>> commit changelogs.  They're helpful in the [00/] message, but not in >>>> the changelogs. >>> >>> But Jesse may still need mark to figure out which one is latest? >> >> The way I do that is with "stg mail -v v3", which puts "[PATCH v3 >> 01/10]" in the subject.  IMO, that's much more useful because when you >> post a 23-patch series, I don't want to be bothered with v1, v2, v3 on >> a per-patch basis. > > For that, I could just sed to replace PATCH to PATCH v3 > >> >> It's true that when you post v2, many of those 23 patches will be >> unchanged from v1, and you do have to describe that in the [v2 00/23] >> mail.  But at least it's easy to identify the entire set of v2 >> patches. > > Version number of the entire set could be different from individual patch. > That could be more confusing. You already post the entire series several times, so you have series v1, series v2, etc. Trying to talk about series v2 and patch v3 within that series is too complicated. The version number of the entire series is enough, in my opinion. Bjorn