Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #141
Difficulty: Easy
The original Unix operating system was not written in assembly language.
True or False?
Linux & Unix Commands - Search Man Pages

git-check-attr(1) [centos man page]

GIT-CHECK-ATTR(1)						    Git Manual							 GIT-CHECK-ATTR(1)

NAME
git-check-attr - Display gitattributes information SYNOPSIS
git check-attr [-a | --all | attr...] [--] pathname... git check-attr --stdin [-z] [-a | --all | attr...] < <list-of-paths> DESCRIPTION
For every pathname, this command will list if each attribute is unspecified, set, or unset as a gitattribute on that pathname. OPTIONS
-a, --all List all attributes that are associated with the specified paths. If this option is used, then unspecified attributes will not be included in the output. --cached Consider .gitattributes in the index only, ignoring the working tree. --stdin Read file names from stdin instead of from the command-line. -z Only meaningful with --stdin; paths are separated with a NUL character instead of a linefeed character. -- Interpret all preceding arguments as attributes and all following arguments as path names. If none of --stdin, --all, or -- is used, the first argument will be treated as an attribute and the rest of the arguments as pathnames. OUTPUT
The output is of the form: <path> COLON SP <attribute> COLON SP <info> LF <path> is the path of a file being queried, <attribute> is an attribute being queried and <info> can be either: unspecified when the attribute is not defined for the path. unset when the attribute is defined as false. set when the attribute is defined as true. <value> when a value has been assigned to the attribute. EXAMPLES
In the examples, the following .gitattributes file is used: *.java diff=java -crlf myAttr NoMyAttr.java !myAttr README caveat=unspecified o Listing a single attribute: $ git check-attr diff org/example/MyClass.java org/example/MyClass.java: diff: java o Listing multiple attributes for a file: $ git check-attr crlf diff myAttr -- org/example/MyClass.java org/example/MyClass.java: crlf: unset org/example/MyClass.java: diff: java org/example/MyClass.java: myAttr: set o Listing all attributes for a file: $ git check-attr --all -- org/example/MyClass.java org/example/MyClass.java: diff: java org/example/MyClass.java: myAttr: set o Listing an attribute for multiple files: $ git check-attr myAttr -- org/example/MyClass.java org/example/NoMyAttr.java org/example/MyClass.java: myAttr: set org/example/NoMyAttr.java: myAttr: unspecified o Not all values are equally unambiguous: $ git check-attr caveat README README: caveat: unspecified SEE ALSO
gitattributes(5). GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-CHECK-ATTR(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 < <list-of-paths> DESCRIPTION
For each pathname given via the command-line or from a file via --stdin, show the pattern from .gitignore (or other input files to the exclude mechanism) that decides if the pathname is excluded or included. Later patterns within a file take precedence over earlier ones. 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. --stdin Read file names from stdin 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. 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> 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) gitconfig(5) git-ls-files(5) GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-CHECK-IGNORE(1)

Featured Tech Videos