Message ID | 20230511133406.78155-1-bagasdotme@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Treewide GPL SPDX conversion (love letter to Didi) | expand |
On Thu, 11 May 2023 20:33:56 +0700 Bagas Sanjaya wrote: > I trigger this patch series because of Didi's GPL full name fixes > attempt [1], for which all of them had been NAKed. In many cases, the > appropriate correction is to use SPDX license identifier instead. > > Often, when replacing license notice boilerplates with their equivalent > SPDX identifier, the notice doesn't mention explicit GPL version. Greg > [2] replied this question by falling back to GPL 1.0 (more precisely > GPL 1.0+ in order to be compatible with GPL 2.0 used by Linux kernel), > although there are exceptions (mostly resolved by inferring from > older patches covering similar situation). Should you be CCing linux-spdx@ on this?
On 5/12/23 07:41, Jakub Kicinski wrote: > On Thu, 11 May 2023 20:33:56 +0700 Bagas Sanjaya wrote: >> I trigger this patch series because of Didi's GPL full name fixes >> attempt [1], for which all of them had been NAKed. In many cases, the >> appropriate correction is to use SPDX license identifier instead. >> >> Often, when replacing license notice boilerplates with their equivalent >> SPDX identifier, the notice doesn't mention explicit GPL version. Greg >> [2] replied this question by falling back to GPL 1.0 (more precisely >> GPL 1.0+ in order to be compatible with GPL 2.0 used by Linux kernel), >> although there are exceptions (mostly resolved by inferring from >> older patches covering similar situation). > > Should you be CCing linux-spdx@ on this? Oops, I forgot to Cc that list. Will do in v2.