Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repo/linux: Remove jsarha #314

Merged
merged 1 commit into from
Sep 25, 2023
Merged

repo/linux: Remove jsarha #314

merged 1 commit into from
Sep 25, 2023

Conversation

groeck
Copy link

@groeck groeck commented Aug 25, 2023

e-mail to [email protected] bounces, and 0-day spams pretty much everyone from this repository. Remove it.

@rli9
Copy link

rli9 commented Aug 26, 2023

Thanks for pointing this out. Sorry, we will change this repo to private so only Jyri Sarha will get the notifcation to avoid spam to others. And I will correct the mail address to be [email protected].

rli9 added a commit that referenced this pull request Aug 26, 2023
@groeck
Copy link
Author

groeck commented Aug 26, 2023 via email

chromeos-4.14 and chromeos-4.19 are close to EOL. While identifying and
fixing real bugs in those branches would still be important, 0-day is
creating too much noise which distracts from real problems. Since there
does not appear to be a means to selectively tell 0-day to not check for
documentation mismatches or other cosmetic issues in older branches (or
anywhere, really), drop coverage of close-to-eol branches to reduce the
noise.

Signed-off-by: Guenter Roeck <[email protected]>
@rli9 rli9 merged commit 5080fe8 into intel:master Sep 25, 2023
3 checks passed
@rli9
Copy link

rli9 commented Sep 25, 2023

thanks for the patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants