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
Given the following a.txt file:
a.txt
1 2 3
and the following working.patch:
working.patch
--- a.txt 2019-03-28 17:02:04.832004033 -0700 +++ b.txt 2019-03-28 17:02:34.999576803 -0700 @@ -1,4 +1,4 @@ -1 +0 2 3
Patching will fail if a.txt.orig already exists:
a.txt.orig
$ touch a.txt.orig $ ./patch.py --debug working.patch && echo Success! DEBUG reading working.patch DEBUG crlf: 0 lf: 5 cr: 0 - file: b.txt hunk: 1 DEBUG - 1 hunks for a.txt DEBUG total files: 1 total hunks: 1 DEBUG normalize filenames DEBUG patch type = plain DEBUG source = a.txt DEBUG target = b.txt DEBUG processing 1/1: a.txt DEBUG hunk no.1 for file a.txt -- is ready to be patched WARNING can't backup original file to a.txt.orig - aborting Success! $ cat a.txt 1 2 3
but the program will exit successfully instead of returning an error.
The text was updated successfully, but these errors were encountered:
Return an error when aborting due to existing .orig file (fixes techt…
6000f33
…onik#60)
Switch python-patch to our fork of it
e6fdcc9
This will prevent silent errors when `.orig` files already exist and interfere with `npm run apply_patches`. See techtonik/python-patch#60.
ca8277c
No branches or pull requests
Given the following
a.txt
file:and the following
working.patch
:Patching will fail if
a.txt.orig
already exists:but the program will exit successfully instead of returning an error.
The text was updated successfully, but these errors were encountered: