Re: [cip-kernel-sec] failure when importing stable
Ben Hutchings <ben.hutchings@...>
On Fri, 2019-06-14 at 05:01 +0000, daniel.sangorrin@...
Hello Ben,So the README should refer to that file rather than repeating a list of
I added a "cip" remote branch, but then I got an error when importingimport_stable.py doesn't update the "torvalds" remote, and neither did
you, so you don't have all the expected tags.
I suppose that import_stable.py should do that.
I am still trying to figure out the correct workflow. I have thoughtNot yet but it would probably not be hard to do.
Also, I wanted to know how new issues are added. I am guessingYou don't need to run validate.py immediately after an import, unless
you suspect a bug in the importer. It's only important after hand-
$ vi issues/CVE-xxx <-- edit by hand those with syntax errors, orYou would edit by hand if you see that some imported information is
incorrect or there is missing information.
$ ./scripts/validate.py <-- repeat validate until no errors appearYAML allows the same thing to be written in different ways, e.g.
bracketed vs bulleted lists. The purpose of cleanup.py is to make the
syntax and ordering of items consistent with the importers, to reduce
"noise" in diffs.
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom