DIRVISH-LOCATE(1) General Commands Manual DIRVISH-LOCATE(1)NAME
dirvish-locate - locate file versions in dirvish images
SYNOPSIS
dirvish-locate vault[:branch] pattern
DESCRIPTION
Locate versions of files in a dirvish vault
The index of each image specified vault is searched for paths matching pattern. Each path found matching the pattern will be reported fol-
lowed by a modification time of each version of the file and all images having a link to it.
The optional branch specification will restrict searching to the specified branch.
Images with an error status will be skipped as will any without index files. The index file may be compressed by gzip or bzip2. See tree
and index in dirvish.conf(5) for details.
The pattern is a perl regular expression to match the final component of the path. Append .* to the end of the pattern if you wish to
match any substring of the whole path or $ if you wish to anchor the pattern to the end of the path. See perlre(1) for details.
Directories are excluded from matching as they would wind up matching every file within them anyway. Symlinks are also excluded from
matching.
If the pattern matches too many paths dirvish-locate will only report the paths matched and not versions. As a sanity check if the number
of matches is really excessive dirvish-locate will limit the number of images searched. Excessive matches is an indication of an insuffi-
ciently specific pattern. Use the resulting path list to compose a more specific one.
EXIT CODES
To facilitate further automation and integration of dirvish-locate with other tools dirvish-locate provides rationalised exit codes. The
exit codes are range based. While the code for a specific error may change from one version to another it will remain within the specified
range. So don't test for specific exit codes but instead test for a range of values. To the degree possible higher value ranges indicate
more severe errors.
0 success 200-219 An error was encountered in loading a configuration file.
220-254
An error was detected in the configuration.
255 Incorrect usage.
FILES
/etc/dirvish/master.conf
alternate master configuration file.
/etc/dirvish.conf
master configuration file.
bank/vault/image/summary
image creation summary.
bank/vault/image/index
bank/vault/image/index.gz
bank/vault/image/index.bz2
dirvish index file.
SEE ALSO dirvish.conf(5)BUGS DIRVISH-LOCATE(1)
Check Out this Related Man Page
GIT-CHECK-IGNORE(1) Git Manual GIT-CHECK-IGNORE(1)NAME
git-check-ignore - Debug gitignore / exclude files
SYNOPSIS
git check-ignore [options] pathname...
git check-ignore [options] --stdin
DESCRIPTION
For each pathname given via the command-line or from a file via --stdin, check whether the file is excluded by .gitignore (or other input
files to the exclude mechanism) and output the path if it is excluded.
By default, tracked files are not shown at all since they are not subject to exclude rules; but see '--no-index'.
OPTIONS -q, --quiet
Don't output anything, just set exit status. This is only valid with a single pathname.
-v, --verbose
Also output details about the matching pattern (if any) for each given pathname. For precedence rules within and between exclude
sources, see gitignore(5).
--stdin
Read pathnames from the standard input, one per line, instead of from the command-line.
-z
The output format is modified to be machine-parseable (see 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.
--no-index
Don't look in the index when undertaking the checks. This can be used to debug why a path became tracked by e.g. git add . and was
not ignored by the rules as expected by the user or when developing patterns including negation to match a path previously added with
git add -f.
OUTPUT
By default, any of the given pathnames which match an ignore pattern will be output, one per line. If no pattern matches a given path,
nothing will be output for that path; this means that path will not be ignored.
If --verbose is specified, the output is a series of lines of the form:
<source> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>
<pathname> is the path of a file being queried, <pattern> is the matching pattern, <source> is the pattern's source file, and <linenum> is
the line number of the pattern within that source. If the pattern contained a ! prefix or / suffix, it will be preserved in the output.
<source> will be an absolute path when referring to the file configured by core.excludesFile, or relative to the repository root when
referring to .git/info/exclude or a per-directory exclude file.
If -z is specified, the pathnames in the output are delimited by the null character; if --verbose is also specified then null characters
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 git(1). The caller is responsible for avoiding deadlocks caused by
overfilling an input buffer or reading from an empty output buffer.
EXIT STATUS
0
One or more of the provided paths is ignored.
1
None of the provided paths are ignored.
128
A fatal error was encountered.
SEE ALSO gitignore(5)git-config(1)git-ls-files(1)GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CHECK-IGNORE(1)