| commit | ac5de4984df282d64feb4af33b92e0a75652e2b6 | |
| author | Eric Blake <eblake@redhat.com> | |
| Tue, 19 Jun 2018 20:39:18 +0000 (19 15:39 -0500) | ||
| committer | Eric Blake <eblake@redhat.com> | |
| Thu, 21 Jun 2018 14:21:19 +0000 (21 09:21 -0500) | ||
| tree | e3f3401992757638a2a80bfedba9e85a7d5007e5 | treesnapshot (tar.gz zip) |
| parent | 46012db666990ff2eed1d3dc199ab8006439a93b | commitdiff |
tests: Simplify .gitignore
Commit 0bcc8e5b was yet another instance of 'git status' reporting
dirty files after an in-tree build, thanks to the new binary
tests/check-block-qdict.
Instead of piecemeal exemptions of each new binary as they are
added, let's use git's negative globbing feature to exempt ALL
files that have a 'test-' or 'check-' prefix, except for the ones
ending in '.c' or '.sh'. We still have a couple of generated
files that then need (re-)exclusion, but the overall list is a
LOT shorter, and less prone to needing future edits.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20180619203918.65450-1-eblake@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Commit 0bcc8e5b was yet another instance of 'git status' reporting
dirty files after an in-tree build, thanks to the new binary
tests/check-block-qdict.
Instead of piecemeal exemptions of each new binary as they are
added, let's use git's negative globbing feature to exempt ALL
files that have a 'test-' or 'check-' prefix, except for the ones
ending in '.c' or '.sh'. We still have a couple of generated
files that then need (re-)exclusion, but the overall list is a
LOT shorter, and less prone to needing future edits.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20180619203918.65450-1-eblake@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
| tests/.gitignore | diffblobblamehistory |