Closed abel-von closed 3 years ago
Hi @abel-von. Thanks for your PR.
I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
@abel-von The cri repo only receives bugfix for release/1.4 or release/1.3. Could you mind to file pr to https://github.com/containerd/containerd first and then backport ? thanks!
@abel-von The cri repo only receives bugfix for release/1.4 or release/1.3. Could you mind to file pr to https://github.com/containerd/containerd first and then backport ? thanks!
https://github.com/containerd/containerd/pull/4825
if the PR is accepted, shall I summit the PR to release/1.4 or release 1.3 here?
@abel-von The cri repo only receives bugfix for release/1.4 or release/1.3. Could you mind to file pr to https://github.com/containerd/containerd first and then backport ? thanks!
if the PR is accepted, shall I summit the PR to release/1.4 or release 1.3 here?
Yes! Thanks!
fix #1612