We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
fetchpatch
fetchpatch2
Creating this tracking issue in case a fetchpatch3 ever gets made. These are notable issues in the fetchpatch{,2} normalization:
fetchpatch3
fetchpatch{,2}
fixes found in the wild:
The text was updated successfully, but these errors were encountered:
For those looking for a workaround, use fetchurl with a https://github.com/.../somehash.diff?full_index=1 url to ensure the hash is stable.
fetchurl
https://github.com/.../somehash.diff?full_index=1
?full_index is discussed here: https://github.com/orgs/community/discussions/46034#discussioncomment-4846112
?full_index
This will not support features like revert = true;
revert = true;
Sorry, something went wrong.
It also seems to mangle concatenated patches that introduce a new file and later patch it, like https://github.com/Alexays/Waybar/compare/Alexays:e7c7ef6...picnoir:f99f08b.patch.
No branches or pull requests
Creating this tracking issue in case a
fetchpatch3
ever gets made. These are notable issues in thefetchpatch{,2}
normalization:fetchpatch
silently strips binary sections #204320fetchpatch2
allows lengths of commit hashes to change #257446fixes found in the wild:
The text was updated successfully, but these errors were encountered: