On 11/21/2016 10:43 PM, Thomas Monjalon wrote:
> Add a check for commits fixing a released bug.
> Such commits are found thanks to scripts/git-log-fixes.sh.
> They must be sent CC: stable at dpdk.org.
> In order to avoid forgetting CC, this mail header can be written
> in the git commit message.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon at 6wind.com>
I think this is useful, thanks for the patch.
> ---
> scripts/check-git-log.sh | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/scripts/check-git-log.sh b/scripts/check-git-log.sh
> index 5f8a9fc..4f98a7a 100755
> --- a/scripts/check-git-log.sh
> +++ b/scripts/check-git-log.sh
> @@ -47,12 +47,14 @@ if [ "$1" = '-h' -o "$1" = '--help' ] ; then
> exit
> fi
>
> +selfdir=$(dirname $(readlink -e $0))
> range=${1:-origin/master..}
>
> commits=$(git log --format='%h' --reverse $range)
> headlines=$(git log --format='%s' --reverse $range)
> bodylines=$(git log --format='%b' --reverse $range)
> fixes=$(git log --format='%h %s' --reverse $range | grep -i ': *fix' | cut
> -d' ' -f1)
> +stablefixes=$($selfdir/git-log-fixes.sh $range | sed '/(N\/A)$/d' | cut -d'
> ' -f2)
This breaks the "check-git-log.sh -N" usage, since "-N" is not a valid
range for git-log-fixes.sh.
Generates warning:
.../scripts/git-log-fixes.sh: illegal option -- 6
usage: git-log-fixes.sh [-h] <git_range>
> tags=$(git log --format='%b' --reverse $range | grep -i -e 'by *:' -e
> 'fix.*:')
> bytag='\(Reported\|Suggested\|Signed-off\|Acked\|Reviewed\|Tested\)-by:'
>
> @@ -191,3 +193,10 @@ bad=$(for fixtag in $fixtags ; do
> printf "$fixtag" | grep -v "^$good$"
> done | sed 's,^,\t,')
> [ -z "$bad" ] || printf "Wrong 'Fixes' reference:\n$bad\n"
> +
> +# check CC:stable for fixes
> +bad=$(for fix in $stablefixes ; do
> + git log --format='%b' -1 $fix | grep -qi '^CC: *stable at dpdk.org' ||
> + git log --format='\t%s' -1 $fix
> +done)
> +[ -z "$bad" ] || printf "Should CC: stable at dpdk.org\n$bad\n"
This is good for developer, but since "CC: xx" tags removed when patch
applied, this will generate warnings when run against existing history.
I don't know what can be done for this.
Or should we keep CC: tags in commit log perhaps?
>
