-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix typos found by codespell #775
Conversation
|
I thought so, that's why I have two commits – one outside |
6808166
to
ae7750a
Compare
it's unknown whether approved changes would be implemented in a local branch or directly into the master branch @anisimkov is unlikely to respond to your ping the relevant
and also these
you further suggest a change as follows -- We allow ZLib to make header only in case of default header type.
- -- Otherwise we would either do header by ourselfs, or do not do
+ -- Otherwise we would either do header by ourselves, or do not do
-- header at all. @hravnx approved these changes to dotzlib
the relevant
@gvollant last year had submitted pulls to this repo the relevant
|
before pursuing any more work on the now ada and minizip separate pulls my suggestion would be to first receive confirmation that the relevant contributors want to spend the time to review updates to their own contributions in terms of typo fixes as pertains to ada that response is unlikely to arrive |
If the initial contributors do not want to spend the time to maintain their code, will it remain as it is forever? What is the rationale behind this decision? It seems at odds with the whole point of open source. |
In any case, I understand ada and minizip are not a priority. I haven't found yet the "relevant PR" you refer to, but I have added the missing typos to the codespell dictionary of typos: codespell-project/codespell#2742 What about changes to zlib itself (this merge request)? |
ae7750a
to
9284be6
Compare
But then how to create pull requests? Pull requests are usually created against the main/master branch. How do I know which branch to create the pull request against? |
Sometimes there are intentions to schedule changes concomitant with an upcoming new release. Occasionally code or bundled code as it were may become described as abandonware or orphanware.
I'm neither designated as a Reviewer nor have I write authority for this repo. AFAIK, pertaining to contrib subdirectories it is not a matter of priorities. the relevant
The master branch in this repo is the correct branch to create the pull request against. Maintainers have their own individual or collective approach to changes in the source code. |
I see, nothing's certain. |
many typo fixes proposed on 7-5-2022 were incorporated on 8-23-2022 |
cf: contrib/minizip/unzip.c this isn't a request but as long at you've submitted a minizip bulk typo fix see also my comment on noting @sredna in that same PR submitted a layout change for a code comment in contrib/minizip/unzip.c |
are somes change linked with #784 ? |
@gvollant It had been suggested I open different merge requests for some subdirectories maintained by their respective contributors:
This merge request #775 fixes typos outside these subdirectories. |
specifically the typos respectively in if this pull is merged then close @hravnx reviewed presumably he has no objections to the fixes added on Feb 18 @gvollant gave a green light on |
@madler: Have you seen? Can you merge it? |
Applied. |
cf: @anisimkov had not responded to the comment of @DimitriPapadopoulos looks like the content of all of the pulls of @DimitriPapadopoulos have been committed to the develop branch |
Merged commit: |
No description provided.