-
Notifications
You must be signed in to change notification settings - Fork 22
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
combinediff is setting incorrect paths to files #53
Open
Roo4L opened this issue
Jul 7, 2022
· 4 comments
· May be fixed by samatcodeapprove/patchutils#1 or #56
Open
combinediff is setting incorrect paths to files #53
Roo4L opened this issue
Jul 7, 2022
· 4 comments
· May be fixed by samatcodeapprove/patchutils#1 or #56
Comments
I have seen this as well! |
samatcodeapprove
added a commit
to samatcodeapprove/patchutils
that referenced
this issue
Feb 2, 2023
This was referenced Feb 2, 2023
Cool , I will try test it this weekend , and give some feedback |
what command did you use to make those patch files? My |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I've face a bug during execution of combinediff. Let's say I have following first and second patch files:
first.patch
second.patch
After executing
combinediff -p1 first.patch second.patch
I get the following output:As you see, the path to the first file is
b
instead ofa
. I understand that it doesn't affect patch applying, but it breaks the convention used by almost all package vendors. Hope you would have a chance to fix it. Thanks in advance!The text was updated successfully, but these errors were encountered: