linux-kernel - Re: [PATCH 00/23] PCI, x86: pci root bus hotplug support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo7dJ4K=4zbpLzs6d_vEp53F89_FuWFDD+6oYCeBidyTPw@mail.gmail.com>
Date:	Fri, 9 Mar 2012 12:10:32 -0700
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bjorn Helgaas <bjorn.helgaas@...il.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>, x86 <x86@...nel.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/23] PCI, x86: pci root bus hotplug support

On Fri, Mar 9, 2012 at 11:55 AM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Fri, Mar 9, 2012 at 9:34 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> On Fri, Mar 9, 2012 at 1:19 AM, Yinghai Lu <yinghai@...nel.org> wrote:
>>> On Thu, Mar 8, 2012 at 4:43 PM, Bjorn Helgaas <bhelgaas@...gle.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/