Skip to content

Conversation

@yselkowitz
Copy link

IBM would like to see this backported to upstream-supported stable branch(es) as well.

@cla-checker-service
Copy link

❌ Author of the following commits did not sign a Contributor Agreement:
6d1e53f

Please, read and sign the above mentioned agreement if you want to contribute to this project

@rjernst
Copy link
Member

rjernst commented Mar 6, 2020

While we have received similar PRs in the past (eg #42901), we feel strongly that we should not add any code, however minor, towards claiming support for platforms or features we cannot test against or support. Thank you for the PR, but we do not plan to merge this commit, so I hope you don't mind that I close this.

@rjernst rjernst closed this Mar 6, 2020
@james-crowley
Copy link

@yselkowitz The PR @rjernst linked has some really good information and a little more explanation on why this PR got closed.

Ideally, I would also like to see support for s390x and ppc64le for Elasticsearch! Especial after what @nealef mentioned with Redhat adding support for s390x and ppc64le on OpenShift.

@yselkowitz Feel free to reach out to me internally to talk more(email on my profile).

@nealef
Copy link

nealef commented Jul 8, 2020

I also have updates for go-seccomp-bpf to enable s390x there as well.

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.

4 participants