Skip to content

spelling: call it null-terminate consistently #17489

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

Closed
wants to merge 4 commits into from

Conversation

bagder
Copy link
Member

@bagder bagder commented May 30, 2025

With a dash, using two Ls. Also for different forms of the word.

Use NULL in all uppercase if it means a zero pointer.

Follow-up to 307b754

bagder added 2 commits May 30, 2025 11:28
With a dash, using two Ls. Also for different forms of the word.

Use NULL in all uppercase if it means a zero pointer.

Follow-up to 307b754
@bagder bagder force-pushed the bagder/null-terminate branch from e154192 to 165270b Compare May 30, 2025 09:31
@bagder bagder marked this pull request as ready for review May 30, 2025 09:39
@testclutch
Copy link

Analysis of PR #17489 at 924b8460:

Test ../../tests/http/test_07_upload.py::TestUpload::test_07_36_upload_30x[h3-301] failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Generated by Testclutch

@bagder bagder closed this in fe81a80 May 30, 2025
@bagder bagder deleted the bagder/null-terminate branch May 30, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants