walkero
/
flawfinder
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

flawfinder.1: Clarify explanation of patchfile option

This commit is contained in:
David A. Wheeler 2014-07-12 22:35:12 -04:00
parent 5a56f2667d
commit af33f0e3e9
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
flawfinder.1
View File

@ -344,14 +344,13 @@ behavior is now the default.
.BI \-\-patch patchfile .BI \-\-patch patchfile
.TP .TP
.BI \-P patchfile .BI \-P patchfile
Only report hits that are changed by the given patch file. Examine the selected files or directories, but only report hits in lines
The patch file must be in unified diff format (e.g., the output of that are added or modified by the given patch file.
"diff -u old new", "svn diff", or "git diff"), The patch file must be in a recognized unified diff format
where the new files are the ones that are (e.g., the output of "diff -u old new", "svn diff", or "git diff [commit]").
being examined by flawfinder.
The files referenced in the patch files are examined, but only the
lines changed in the patch are reported on.
Flawfinder assumes that the patch has already been applied to the files. Flawfinder assumes that the patch has already been applied to the files.
The patch file can also include changes to irrelevant files
(they will simply be ignored).
The line numbers given in the patch file are used to determine which The line numbers given in the patch file are used to determine which
lines were changed, so if you have modified the files since the lines were changed, so if you have modified the files since the
patch file was created, regenerate the patch file first. patch file was created, regenerate the patch file first.