summaryrefslogtreecommitdiffstats
path: root/git-check-ignore.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-05-29 16:57:17 -0700
committerJunio C Hamano <gitster@pobox.com>2013-05-29 16:57:17 -0700
commitc710296399a86586e3a5e24ea8519ea2442ab7cf (patch)
treeeb0d0bf25b3098a12d15f4a2921f16ecaaa2756f /git-check-ignore.txt
parentb6595471f5299e8b13181e09072b486dd0ad6261 (diff)
downloadgit-htmldocs-c710296399a86586e3a5e24ea8519ea2442ab7cf.tar.gz
Autogenerated HTML docs for v1.8.3-101-g727a4
Diffstat (limited to 'git-check-ignore.txt')
-rw-r--r--git-check-ignore.txt20
1 files changed, 20 insertions, 0 deletions
diff --git a/git-check-ignore.txt b/git-check-ignore.txt
index 854e4d0c4..8e1f7ab7e 100644
--- a/git-check-ignore.txt
+++ b/git-check-ignore.txt
@@ -39,6 +39,12 @@ OPTIONS
below). If `--stdin` is also given, input paths are separated
with a NUL character instead of a linefeed character.
+-n, --non-matching::
+ Show given paths which don't match any pattern. This only
+ makes sense when `--verbose` is enabled, otherwise it would
+ not be possible to distinguish between paths which match a
+ pattern and those which don't.
+
OUTPUT
------
@@ -65,6 +71,20 @@ are also used instead of colons and hard tabs:
<source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>
+If `-n` or `--non-matching` are specified, non-matching pathnames will
+also be output, in which case all fields in each output record except
+for <pathname> will be empty. This can be useful when running
+non-interactively, so that files can be incrementally streamed to
+STDIN of a long-running check-ignore process, and for each of these
+files, STDOUT will indicate whether that file matched a pattern or
+not. (Without this option, it would be impossible to tell whether the
+absence of output for a given file meant that it didn't match any
+pattern, or that the output hadn't been generated yet.)
+
+Buffering happens as documented under the `GIT_FLUSH` option in
+linkgit:git[1]. The caller is responsible for avoiding deadlocks
+caused by overfilling an input buffer or reading from an empty output
+buffer.
EXIT STATUS
-----------