Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Examples: $ ./scripts/report_affect

Hello Ben, I think this should be fine. You need to remove the cached file import/stable_branches.yml [cip-kernel-sec][RESEND v3] report_affected: add support for To be honest, I am not 100% sure that

Sorry, I went too fast. I should have moved the regexp to get_base_ver_stable_branch. I will resend. Thanks, Daniel

[...] Thanks, you are right. I have used re.escape('.'). I didn't know this function, it's really useful not having to remember how to escape characters (I figured out I could have used \\.). I think

Rather than looking up each issue file, I would like to have an overview of what each CVE ID means. Example: $ ./scripts/report_affected.py --show-description linux-4.4.y-cip Signed-off-by: Daniel San

Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Examples: $ ./scripts/report_affect

Hello Ben, Thanks again for your detailed reviews. I have fixed the tags patch with your suggestions. I will reply to them separately. [cip-kernel-sec][RESEND v2 1/2] report_affected: add support for

Glad to hear about the importance. Other members also expressed their interest. Sorry about that. The new version only makes copies when necessary (one copy per branch name supplied by the user). OK,

Yes, you are right. I came up with exactly the same solution. Thanks, Daniel

I was taking the approach of "doing as much as possible". Something like what a recovery tool does on a disk with broken sectors: if a broken sector is found skip it. In the new version, the script wi

Rather than looking up each issue file, I would like to have an overview of what each CVE ID means. Example: $ ./scripts/report_affected.py --show-description linux-4.4.y-cip Signed-off-by: Daniel San

These were distracting when checking new code. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- scripts/import_stable.py | 8 +++++--- scripts/kernel_sec/branch.py | 4 ++-- scripts/

Reporting on tags is useful for product engineers that have shipped a kernel with a specific tag and need to know which issues affect their product after some time. Examples: $ ./scripts/report_affect

The previous code could not handle branches with names other than stable branch names. For example, passing "linux-4.4.y-cip" as a branch would return an error. Signed-off-by: Daniel Sangorrin <daniel

Helper script that prepares the local git repository with the configured remote branches. Expert developers and kernel maintainers will probably have their own worktrees but for new users or a quickst

Add checks to make sure that the local repository exists and has the configured remotes in place. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- scripts/import_stable.py | 1 + sc

Hello Ben, Thank you for the detailed review, and sorry for the delay. I have modified my patch series taking your comments into account. Note: I will reply to your comments separately I re-send to yo

It seems that a lot of people have the same problem. https://gitlab.com/gitlab-org/gitlab-ce/issues/15041

Hello Ben, I'm not sure where the script that imports new issues and sends these e-mails is located, but it looks like it is not calling "scripts/cleanup.py". I run cleanup.py, and I noticed that it m

Rather than looking up each issue file, I would like to have an overview of what each CVE ID means. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- scripts/report_affected.py | 24