Re: license: comma or semicolon?

[Mike Frysinger]

On 03 Jan 2022 00:26, Bernhard Voelker wrote:
> Comparing some of the license headers, I found that some modules are using a 
> comma or
> a semicolon in the 3rd line of the text:
> 
>   $ ~/gnulib> GIT_PAGER= git grep -B2 -A1 'either version' -- doc/gpl-3.0.texi
>   doc/gpl-3.0.texi-This program is free software: you can redistribute it 
> and/or modify
>   doc/gpl-3.0.texi-it under the terms of the GNU General Public License as 
> published by
>   doc/gpl-3.0.texi:the Free Software Foundation, either version 3 of the 
> License, or (at
>   doc/gpl-3.0.texi-your option) any later version.
> 
> Here are some numbers:
> 
>   $ for f in coreutils findutils grep gnulib hello sed; do \
>       printf '%10s: %4d %4d\n' $f \
>         $( git -C $f grep 'the Free Software Foundation, either version 3 of 
> the License' | wc -l ) \
>         $( git -C $f grep 'the Free Software Foundation; either version 3 of 
> the License' | wc -l ); \
>     done
>  coreutils:  778    8
>  findutils:   94    2
>       grep:   43    1
>     gnulib:   47 1905
>      hello:    4    2
>        sed:   82    1
> 
> Shouldn't we change all to ',' - as in 'gpl-3.0.texi'?

according to gnu.org, it should be a comma.
https://www.gnu.org/licenses/gpl-3.0.html#howto
    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.
-mike

signature.asc
Description: PGP signature