[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b79dcf81-2eb4-c376-e1a8-e947ffa6c70a@nexus-software.ie>
Date: Thu, 4 May 2023 15:28:10 +0100
From: Bryan O'Donoghue <pure.logic@...us-software.ie>
To: Vikash Garodia <quic_vgarodia@...cinc.com>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Dikshita Agarwal <quic_dikshita@...cinc.com>,
linux-media@...r.kernel.org, stanimir.k.varbanov@...il.com,
agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
mchehab@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 0/4] venus: add support for 10 bit decoding
On 04/05/2023 15:04, Vikash Garodia wrote:
>> Doh I see you did most of that - just missed the V2.
>>
>> Please remember to version your subsequent series. "git format-patch -v2"
>
> Does this qualify for a version upgrade when a single patch is
> subsequently raised as series ? IMO, the link
>
> to previous single patch in cover letter and then starting the series
> (as v0) seems to provide the required info.
Hmm. I'd say any series should have an increment in it to differentiate,
with the exception being RESEND.
Also you are splitting one patch into four.
Looking through a bunch of email it might be not immediately obvious to
understand that the new series and old series differ, which is IMO how
the version numbers help others to know what's going on.
---
bod
Powered by blists - more mailing lists