messages by lauching an editor uses the value of this
variable when it is set, and the environment variable
`GIT_EDITOR` is not set. The order of preference is
- `GIT_EDITOR` environment, `core.editor`, `EDITOR` and
- `VISUAL` environment variables and then finally `vi`.
+ `GIT_EDITOR` environment, `core.editor`, `VISUAL` and
+ `EDITOR` environment variables and then finally `vi`.
core.pager::
The command that git will use to paginate output. Can be overridden
messages by lauching an editor uses the value of this\r
variable when it is set, and the environment variable\r
<tt>GIT_EDITOR</tt> is not set. The order of preference is\r
- <tt>GIT_EDITOR</tt> environment, <tt>core.editor</tt>, <tt>EDITOR</tt> and\r
- <tt>VISUAL</tt> environment variables and then finally <tt>vi</tt>.\r
+ <tt>GIT_EDITOR</tt> environment, <tt>core.editor</tt>, <tt>VISUAL</tt> and\r
+ <tt>EDITOR</tt> environment variables and then finally <tt>vi</tt>.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 20-Jul-2007 10:27:37 UTC\r
+Last updated 22-Jul-2007 09:33:18 UTC\r
</div>\r
</div>\r
</body>\r
[ --cherry-pick ]\r
[ --encoding[=<encoding>] ]\r
[ --(author|committer|grep)=<pattern> ]\r
- [ --regexp-ignore-case ] [ --extended-regexp ]\r
+ [ --regexp-ignore-case | \-i ]\r
+ [ --extended-regexp | \-E ]\r
[ --date={local|relative|default|iso|rfc|short} ]\r
[ [--objects | --objects-edge] [ --unpacked ] ]\r
[ --pretty | --header ]\r
</p>\r
</dd>\r
<dt>\r
---regexp-ignore-case\r
+-i, --regexp-ignore-case\r
</dt>\r
<dd>\r
<p>\r
</p>\r
</dd>\r
<dt>\r
---extended-regexp\r
+-E, --extended-regexp\r
</dt>\r
<dd>\r
<p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:52 UTC\r
+Last updated 22-Jul-2007 09:33:18 UTC\r
</div>\r
</div>\r
</body>\r
[ \--cherry-pick ]
[ \--encoding[=<encoding>] ]
[ \--(author|committer|grep)=<pattern> ]
- [ \--regexp-ignore-case ] [ \--extended-regexp ]
+ [ \--regexp-ignore-case | \-i ]
+ [ \--extended-regexp | \-E ]
[ \--date={local|relative|default|iso|rfc|short} ]
[ [\--objects | \--objects-edge] [ \--unpacked ] ]
[ \--pretty | \--header ]
Limit the commits output to ones with log message that
matches the specified pattern (regular expression).
---regexp-ignore-case::
+-i, --regexp-ignore-case::
Match the regexp limiting patterns without regard to letters case.
---extended-regexp::
+-E, --extended-regexp::
Consider the limiting patterns to be extended regular expressions
instead of the default basic regular expressions.
pattern.</p>\r
<p>When deciding whether to ignore a path, git normally checks\r
<tt>gitignore</tt> patterns from multiple sources, with the following\r
-order of precedence:</p>\r
+order of precedence, from highest to lowest (within one level of\r
+precedence, the last matching pattern decides the outcome):</p>\r
<ul>\r
<li>\r
<p>\r
-Patterns read from the file specified by the configuration\r
- variable <em>core.excludesfile</em>.\r
-</p>\r
-</li>\r
-<li>\r
-<p>\r
-Patterns read from <tt>$GIT_DIR/info/exclude</tt>.\r
+Patterns read from the command line for those commands that support\r
+ them.\r
</p>\r
</li>\r
<li>\r
<p>\r
Patterns read from a <tt>.gitignore</tt> file in the same directory\r
- as the path, or in any parent directory, ordered from the\r
- deepest such file to a file in the root of the repository.\r
+ as the path, or in any parent directory, with patterns in the\r
+ higher level files (up to the root) being overriden by those in\r
+ lower level files down to the directory containing the file.\r
These patterns match relative to the location of the\r
<tt>.gitignore</tt> file. A project normally includes such\r
<tt>.gitignore</tt> files in its repository, containing patterns for\r
files generated as part of the project build.\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+Patterns read from <tt>$GIT_DIR/info/exclude</tt>.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+Patterns read from the file specified by the configuration\r
+ variable <em>core.excludesfile</em>.\r
+</p>\r
+</li>\r
</ul>\r
<p>The underlying git plumbing tools, such as\r
<a href="git-ls-files.html">git-ls-files(1)</a> and <a href="git-read-tree.html">git-read-tree(1)</a>, read\r
<p>\r
An optional prefix <em>!</em> which negates the pattern; any\r
matching file excluded by a previous pattern will become\r
- included again.\r
+ included again. If a negated pattern matches, this will\r
+ override lower precedence patterns sources.\r
</p>\r
</li>\r
<li>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:10:00 UTC\r
+Last updated 22-Jul-2007 09:33:20 UTC\r
</div>\r
</div>\r
</body>\r
When deciding whether to ignore a path, git normally checks
`gitignore` patterns from multiple sources, with the following
-order of precedence:
+order of precedence, from highest to lowest (within one level of
+precedence, the last matching pattern decides the outcome):
- * Patterns read from the file specified by the configuration
- variable 'core.excludesfile'.
-
- * Patterns read from `$GIT_DIR/info/exclude`.
+ * Patterns read from the command line for those commands that support
+ them.
* Patterns read from a `.gitignore` file in the same directory
- as the path, or in any parent directory, ordered from the
- deepest such file to a file in the root of the repository.
+ as the path, or in any parent directory, with patterns in the
+ higher level files (up to the root) being overriden by those in
+ lower level files down to the directory containing the file.
These patterns match relative to the location of the
`.gitignore` file. A project normally includes such
`.gitignore` files in its repository, containing patterns for
files generated as part of the project build.
+ * Patterns read from `$GIT_DIR/info/exclude`.
+
+ * Patterns read from the file specified by the configuration
+ variable 'core.excludesfile'.
+
The underlying git plumbing tools, such as
gitlink:git-ls-files[1] and gitlink:git-read-tree[1], read
`gitignore` patterns specified by command-line options, or from
- An optional prefix '!' which negates the pattern; any
matching file excluded by a previous pattern will become
- included again.
+ included again. If a negated pattern matches, this will
+ override lower precedence patterns sources.
- If the pattern does not contain a slash '/', git treats it as
a shell glob pattern and checks for a match against the
projects / git.git / commitdiff