From 5e61527c04bcccce67e2cd285581c004595712b3 Mon Sep 17 00:00:00 2001 From: Danny Scott Date: Wed, 28 Feb 2018 18:48:52 +0100 Subject: [PATCH] Fix typos and shell syntax in the release instructions Closes #18095. --- docs/contributing/how-to-release.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/contributing/how-to-release.md b/docs/contributing/how-to-release.md index c3e5ff9e1b6b..eeeeabd7ed6b 100644 --- a/docs/contributing/how-to-release.md +++ b/docs/contributing/how-to-release.md @@ -20,7 +20,7 @@ Add the missing installed folder locations of any executables to your Path. For the stable (even) releases only, check that binary compatibility hasn't been broken since the last stable release. -### Checking under Unix systems using `abi-complicance-checker` tool. +### Checking under Unix systems using `abi-compliance-checker` tool. Instructions: @@ -32,11 +32,11 @@ Instructions: 1. Create directories for temporary files containing the ABI dumps for the old and new libraries: `mkdir -p ../compat/{$old,$new}`. 1. Run abi-dumper on all libraries: `for l in $old/lib/*.so; do abi-dumper $l - -lver $old -o ../compat/$old/$(basename $l).dump` and the same thing with + -lver $old -o ../compat/$old/$(basename $l).dump; done` and the same thing with the new libraries. 1. Run abi-compliance-checker on each pair of produced dumps to generate HTML - reports: `for l in 3.0.2/*dump; abi-compliance-checker -l $(basename $l - .dump) -old $l -new 3.0.3/$(basename $l)`. + reports: `for l in 3.0.2/*dump; do abi-compliance-checker -l $(basename $l + .dump) -old $l -new 3.0.3/$(basename $l); done`. 1. Examine these reports, paying attention to the problem summary. ### Checking under MSW systems.