fix: rename patch file #196
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hey, I actually just merged another patch which takes |
sipasing
force-pushed
the
rename-patch-file
branch
from
eca407d to
e100e79
Compare
Contributor
Author
|
hehe. Done. |
dbenoit17
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems between the time of filing PR #190 and the time of merging it, another patch file with same number (15) prefix was added to main branch.
patches/015-fix-linkage.patch
patches/015-add-hash-sign-verify.patch
Since the filenames are actually different, this shouldn't make any difference at runtime, but it would be good to renumber them for sanity.