| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
guards -w prints the guards in the output stream.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This closes the bug #21114 on Savannah.
|
| |
|
|
|
|
| |
(even if I'm not sure why the previous version breaks)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Timestamp comparisons when popping a patch were fixed in commit
005922085f0135c35baa4b0e8db6f05d78586377, so we can get rid of this
sleep in the test suite.
|
|
|
|
|
|
|
|
|
|
| |
Support for obsolete find -perm +MODE syntax was removed from GNU
findutils by commit
v4.5.10-144-g90f0c5d24153ad3327edd6f2249fc95a5cfb72e0.
Reported by Dmitry V. Levin.
Also -maxdepth is not portable and not needed so drop it.
|
|
|
|
|
| |
Add support for multiple files to "quilt patches". Patches will be
printed, that modify any of the listed files.
|
|
|
|
|
| |
Let "quilt patches" also match deleted files in unapplied patches.
Commit 4df47975 was supposed to fix that already, but did not really.
|
|
|
|
|
|
|
| |
Commit 2e581933 added a parameter to function scan_unapplied but the
corresponding shift wasn't adjusted accordingly. Apparently this bug
was harmless but there is a slight performance penalty so let's fix
it still.
|
| |
|
| |
|
|
|
|
| |
commands accepting it
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It should make no difference if the parser is right, but will make it
easier to spot bugs in said parser.
|
|
|
|
|
|
| |
As a bug was recently found in this script, add a test case covering
both unified and context patch formats, so that hopefully no other
bug creeps in in the future.
|
|
|
|
|
|
|
|
|
| |
the script for trailing whitespace removal fails for me if a
context diff has an "delete-only" chunk at the end. The following
patch fixes this for me.
[JD: Add one more check for when the "delete-only" chunk is
not at the end.]
|
|
|
|
|
| |
When a helper script is called directly from a test case, it must be
added to the dependencies for that test case.
|
|
|
|
|
| |
Sort the output of remove-trailing-ws for predictable output. This is
needed to include remove-trailing-ws in the test suite.
|
|
|
|
|
|
|
| |
If told to refresh a patch and the patch is empty, still obey. The
user should know what he/she is doing. If the patch was non-empty
before, we must erase it, otherwise a subsequent pop will fail,
complaining that the patch should be refreshed.
|
|
|
|
|
|
|
|
| |
We have to patch temporary files when checking if a patch can be
popped without losing pending changes. When this fails, the status
code we get from "patch" isn't accurate enough to draw conclusions
so don't even try. Just compare the result with the current working
files and tell the user if there is any difference or not.
|
|
|
|
|
|
| |
push:apply_patch() uses --force by default but pop:check_for_pending_changes()
does not. This leads to a problem when trying to pop a patch that changes
files which were originally read-only: patch refuses to touch them.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
While bash allows poking at a function caller's variables, that's
not something we normally do in quilt.
|
|
|
|
|
|
|
|
|
|
|
|
| |
avoids errors like this:
$ quilt refresh
sed: -e expression #1, char 21: unknown option to `s'
Nothing in patch patches/strange:name
[Satoru Takeuchi: suggested first alternative implementation not
relying on find -printf.]
[Jean Delvare: added missing quoting and a new test file for this
case.]
|
|
|
|
|
|
| |
Let the user force pushing a patch even if patch returns with error
code 2. The user should know better. This happens when pushing a
patch with a header but no actual contents, for example.
|
|
|
|
|
|
|
|
|
| |
The timestamps recorded on file systems have a limited resolution.
For this reason, a patch or file with a timestamp exactly equal to
.timestamp should be considered as more recent than .timestamp, i.e.
potentially modified since the last push or refresh. This is
particularly important for the test suite, as we can do many actions
in the same second there.
|
|
|
|
|
| |
Anonymous contribution from the bug tracker:
https://savannah.nongnu.org/bugs/index.php?37495
|