[<prev] [next>] [day] [month] [year] [list]
Message-ID: <PH0PR11MB5673918AB1E9A01FE229ECB4CB29A@PH0PR11MB5673.namprd11.prod.outlook.com>
Date: Mon, 3 Jul 2023 10:19:13 +0000
From: "Lee, Kah Jing" <kah.jing.lee@...el.com>
To: Markus Elfring <Markus.Elfring@....de>,
"Yuslaimi, Alif Zakuan" <alif.zakuan.yuslaimi@...el.com>,
Conor Dooley <Conor.Dooley@...rochip.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"Catalin Marinas" <catalin.marinas@....com>,
Conor Dooley <conor+dt@...nel.org>,
"Dinh Nguyen" <dinguyen@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
"Will Deacon" <will@...nel.org>
Subject: RE: [v4] arm64: dts: agilex/stratix10: Updated QSPI Flash layout for
UBIFS
> >> * Would an other listing style become nicer for the “patch changelog”?
> >
> > This is a complete waste of contributor time.
>
> I would like to point further possibilities out once more.
>
> The arrow notation is also demonstrated in the Linux development
> documentation.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu
> mentation/process/submitting-patches.rst?h=v6.4#n698
>
> Various patches show that more succinct version identifiers are also accepted.
> If a bit of duplicate data can be avoided in the version history, the
> maintenance of corresponding version descriptions can be improved
> accordingly.
Hi Markus,
Do you suggest to use following?
Changelog:
V2: Changes in v2 xxx
V1: Changes in v1 xxx
A bit lost on the suggestion here.
>
> Regards,
> Markus
Powered by blists - more mailing lists