docs/manual: 'Fixes' tag needs a colon
PATCH 1/1 docs/manual: 'Fixes' tag needs a colon
Apparently, patchwork only recognizes the 'Fixes' tag if it is followed by a colon. So make sure the manual documents it as such.
Cc Bernd Kuhls <[email protected]>
--- docs/manual/contribute.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
docs/manual/contribute.txt +1 -1
@@ -73,7 +73,7 @@ basically two things that can be done: In the commit message of a patch fixing an autobuild failure, add a reference to the build result directory, as follows: --------------------- -Fixes http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069 +Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069 --------------------- === Reviewing and testing patches
Signature · 1 line
2.21.0
PATCH 1/1 docs/manual: 'Fixes' tag needs a colon
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> writes:
Apparently, patchwork only recognizes the 'Fixes' tag if it is followed by a colon. So make sure the manual documents it as such.
Cc Bernd Kuhls <[email protected]>
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 docs/manual: 'Fixes' tag needs a colon
In reply to Arnout Vandecappelle (Essensium/Mind)Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> writes:
Apparently, patchwork only recognizes the 'Fixes' tag if it is followed by a colon. So make sure the manual documents it as such.
Cc Bernd Kuhls <[email protected]>
Committed to 2019.02.x and 2019.05.x, thanks.
Signature · 1 line
Bye, Peter Korsgaard