Sebastiaan van Stijn e34ab5200d fix formatting of "nolint" tags for go1.19 ... The correct formatting for machine-readable comments is; //<some alphanumeric identifier>:<options>[,<option>...][ // comment] Which basically means: - MUST NOT have a space before `<identifier>` (e.g. `nolint`) - Identified MUST be alphanumeric - MUST be followed by a colon - MUST be followed by at least one `<option>` - Optionally additional `<options>` (comma-separated) - Optionally followed by a comment Any other format will not be considered a machine-readable comment by `gofmt`, and thus formatted as a regular comment. Note that this also means that a `//nolint` (without anything after it) is considered invalid, same for `//#nosec` (starts with a `#`). Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 4f08346686) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2022-07-15 13:45:13 +02:00
..
diagnostic	all: replace strings.Replace with strings.ReplaceAll	2022-05-09 19:45:40 +08:00
networkdb-test	fix formatting of "nolint" tags for go1.19	2022-07-15 13:45:13 +02:00
ovrouter	Update to Go 1.17.0, and gofmt with Go 1.17	2021-08-24 23:33:27 +02:00
readme_test	Fixup libnetwork lint errors	2021-06-01 23:48:32 +00:00
ssd	fix typo (cluser -> cluster)	2022-06-27 15:12:14 +02:00