2007-11-15 14:19:29 +01:00
|
|
|
// Please don't remove this comment as asciidoc behaves badly when
|
|
|
|
|
// the first non-empty line is ifdef/ifndef. The symptom is that
|
|
|
|
|
// without this comment the <git-diff-core> attribute conditionally
|
|
|
|
|
// defined below ends up being defined unconditionally.
|
|
|
|
|
// Last checked with asciidoc 7.0.2.
|
|
|
|
|
|
|
|
|
|
ifndef::git-format-patch[]
|
|
|
|
|
ifndef::git-diff[]
|
2007-11-01 15:57:40 +01:00
|
|
|
ifndef::git-log[]
|
2007-11-15 14:19:29 +01:00
|
|
|
:git-diff-core: 1
|
2007-11-01 15:57:40 +01:00
|
|
|
endif::git-log[]
|
2007-11-15 14:19:29 +01:00
|
|
|
endif::git-diff[]
|
|
|
|
|
endif::git-format-patch[]
|
|
|
|
|
|
|
|
|
|
ifdef::git-format-patch[]
|
|
|
|
|
-p::
|
2009-11-07 10:58:55 +01:00
|
|
|
--no-stat::
|
2009-11-07 10:51:56 +01:00
|
|
|
Generate plain patches without any diffstats.
|
2007-11-15 14:19:29 +01:00
|
|
|
endif::git-format-patch[]
|
|
|
|
|
|
|
|
|
|
ifndef::git-format-patch[]
|
2005-07-13 21:52:35 +02:00
|
|
|
-p::
|
2008-12-29 08:03:17 +01:00
|
|
|
-u::
|
2010-05-13 10:59:00 +02:00
|
|
|
--patch::
|
2007-11-15 14:19:29 +01:00
|
|
|
Generate patch (see section on generating patches).
|
2015-05-14 06:34:48 +02:00
|
|
|
ifdef::git-diff[]
|
|
|
|
|
This is the default.
|
|
|
|
|
endif::git-diff[]
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2013-07-16 10:05:39 +02:00
|
|
|
-s::
|
|
|
|
|
--no-patch::
|
|
|
|
|
Suppress diff output. Useful for commands like `git show` that
|
|
|
|
|
show the patch by default, or to cancel the effect of `--patch`.
|
2016-03-27 23:26:07 +02:00
|
|
|
endif::git-format-patch[]
|
2013-07-16 10:05:39 +02:00
|
|
|
|
2020-12-21 16:19:59 +01:00
|
|
|
ifdef::git-log[]
|
2021-04-13 13:41:18 +02:00
|
|
|
--diff-merges=(off|none|on|first-parent|1|separate|m|combined|c|dense-combined|cc)::
|
2020-12-21 16:19:59 +01:00
|
|
|
--no-diff-merges::
|
|
|
|
|
Specify diff format to be used for merge commits. Default is
|
|
|
|
|
{diff-merges-default} unless `--first-parent` is in use, in which case
|
|
|
|
|
`first-parent` is the default.
|
|
|
|
|
+
|
|
|
|
|
--diff-merges=(off|none):::
|
|
|
|
|
--no-diff-merges:::
|
|
|
|
|
Disable output of diffs for merge commits. Useful to override
|
|
|
|
|
implied value.
|
|
|
|
|
+
|
2021-04-13 13:41:18 +02:00
|
|
|
--diff-merges=on:::
|
|
|
|
|
--diff-merges=m:::
|
|
|
|
|
-m:::
|
|
|
|
|
This option makes diff output for merge commits to be shown in
|
Revert 'diff-merges: let "-m" imply "-p"'
This reverts commit f5bfcc823ba242a46e20fb6f71c9fbf7ebb222fe, which
made "git log -m" imply "--patch" by default. The logic was that
"-m", which makes diff generation for merges perform a diff against
each parent, has no use unless I am viewing the diff, so we could save
the user some typing by turning on display of the resulting diff
automatically. That wasn't expected to adversely affect scripts
because scripts would either be using a command like "git diff-tree"
that already emits diffs by default or would be combining -m with a
diff generation option such as --name-status. By saving typing for
interactive use without adversely affecting scripts in the wild, it
would be a pure improvement.
The problem is that although diff generation options are only relevant
for the displayed diff, a script author can imagine them affecting
path limiting. For example, I might run
git log -w --format=%H -- README
hoping to list commits that edited README, excluding whitespace-only
changes. In fact, a whitespace-only change is not TREESAME so the use
of -w here has no effect (since we don't apply these diff generation
flags to the diff_options struct rev_info::pruning used for this
purpose), but the documentation suggests that it should work
Suppose you specified foo as the <paths>. We shall call
commits that modify foo !TREESAME, and the rest TREESAME. (In
a diff filtered for foo, they look different and equal,
respectively.)
and a script author who has not tested whitespace-only changes
wouldn't notice.
Similarly, a script author could include
git log -m --first-parent --format=%H -- README
to filter the first-parent history for commits that modified README.
The -m is a no-op but it reflects the script author's intent. For
example, until 1e20a407fe2 (stash list: stop passing "-m" to "git
log", 2021-05-21), "git stash list" did this.
As a result, we can't safely change "-m" to imply "-p" without fear of
breaking such scripts. Restore the previous behavior.
Noticed because Rust's src/bootstrap/bootstrap.py made use of this
same construct: https://github.com/rust-lang/rust/pull/87513. That
script has been updated to omit the unnecessary "-m" option, but we
can expect other scripts in the wild to have similar expectations.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-08-06 03:45:23 +02:00
|
|
|
the default format. `-m` will produce the output only if `-p`
|
|
|
|
|
is given as well. The default format could be changed using
|
2021-04-13 13:41:18 +02:00
|
|
|
`log.diffMerges` configuration parameter, which default value
|
Revert 'diff-merges: let "-m" imply "-p"'
This reverts commit f5bfcc823ba242a46e20fb6f71c9fbf7ebb222fe, which
made "git log -m" imply "--patch" by default. The logic was that
"-m", which makes diff generation for merges perform a diff against
each parent, has no use unless I am viewing the diff, so we could save
the user some typing by turning on display of the resulting diff
automatically. That wasn't expected to adversely affect scripts
because scripts would either be using a command like "git diff-tree"
that already emits diffs by default or would be combining -m with a
diff generation option such as --name-status. By saving typing for
interactive use without adversely affecting scripts in the wild, it
would be a pure improvement.
The problem is that although diff generation options are only relevant
for the displayed diff, a script author can imagine them affecting
path limiting. For example, I might run
git log -w --format=%H -- README
hoping to list commits that edited README, excluding whitespace-only
changes. In fact, a whitespace-only change is not TREESAME so the use
of -w here has no effect (since we don't apply these diff generation
flags to the diff_options struct rev_info::pruning used for this
purpose), but the documentation suggests that it should work
Suppose you specified foo as the <paths>. We shall call
commits that modify foo !TREESAME, and the rest TREESAME. (In
a diff filtered for foo, they look different and equal,
respectively.)
and a script author who has not tested whitespace-only changes
wouldn't notice.
Similarly, a script author could include
git log -m --first-parent --format=%H -- README
to filter the first-parent history for commits that modified README.
The -m is a no-op but it reflects the script author's intent. For
example, until 1e20a407fe2 (stash list: stop passing "-m" to "git
log", 2021-05-21), "git stash list" did this.
As a result, we can't safely change "-m" to imply "-p" without fear of
breaking such scripts. Restore the previous behavior.
Noticed because Rust's src/bootstrap/bootstrap.py made use of this
same construct: https://github.com/rust-lang/rust/pull/87513. That
script has been updated to omit the unnecessary "-m" option, but we
can expect other scripts in the wild to have similar expectations.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-08-06 03:45:23 +02:00
|
|
|
is `separate`.
|
2021-04-13 13:41:18 +02:00
|
|
|
+
|
2020-12-21 16:19:59 +01:00
|
|
|
--diff-merges=first-parent:::
|
|
|
|
|
--diff-merges=1:::
|
|
|
|
|
This option makes merge commits show the full diff with
|
|
|
|
|
respect to the first parent only.
|
|
|
|
|
+
|
|
|
|
|
--diff-merges=separate:::
|
|
|
|
|
This makes merge commits show the full diff with respect to
|
|
|
|
|
each of the parents. Separate log entry and diff is generated
|
Revert 'diff-merges: let "-m" imply "-p"'
This reverts commit f5bfcc823ba242a46e20fb6f71c9fbf7ebb222fe, which
made "git log -m" imply "--patch" by default. The logic was that
"-m", which makes diff generation for merges perform a diff against
each parent, has no use unless I am viewing the diff, so we could save
the user some typing by turning on display of the resulting diff
automatically. That wasn't expected to adversely affect scripts
because scripts would either be using a command like "git diff-tree"
that already emits diffs by default or would be combining -m with a
diff generation option such as --name-status. By saving typing for
interactive use without adversely affecting scripts in the wild, it
would be a pure improvement.
The problem is that although diff generation options are only relevant
for the displayed diff, a script author can imagine them affecting
path limiting. For example, I might run
git log -w --format=%H -- README
hoping to list commits that edited README, excluding whitespace-only
changes. In fact, a whitespace-only change is not TREESAME so the use
of -w here has no effect (since we don't apply these diff generation
flags to the diff_options struct rev_info::pruning used for this
purpose), but the documentation suggests that it should work
Suppose you specified foo as the <paths>. We shall call
commits that modify foo !TREESAME, and the rest TREESAME. (In
a diff filtered for foo, they look different and equal,
respectively.)
and a script author who has not tested whitespace-only changes
wouldn't notice.
Similarly, a script author could include
git log -m --first-parent --format=%H -- README
to filter the first-parent history for commits that modified README.
The -m is a no-op but it reflects the script author's intent. For
example, until 1e20a407fe2 (stash list: stop passing "-m" to "git
log", 2021-05-21), "git stash list" did this.
As a result, we can't safely change "-m" to imply "-p" without fear of
breaking such scripts. Restore the previous behavior.
Noticed because Rust's src/bootstrap/bootstrap.py made use of this
same construct: https://github.com/rust-lang/rust/pull/87513. That
script has been updated to omit the unnecessary "-m" option, but we
can expect other scripts in the wild to have similar expectations.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-08-06 03:45:23 +02:00
|
|
|
for each parent.
|
2020-12-21 16:19:59 +01:00
|
|
|
+
|
|
|
|
|
--diff-merges=combined:::
|
|
|
|
|
--diff-merges=c:::
|
|
|
|
|
-c:::
|
|
|
|
|
With this option, diff output for a merge commit shows the
|
|
|
|
|
differences from each of the parents to the merge result
|
|
|
|
|
simultaneously instead of showing pairwise diff between a
|
|
|
|
|
parent and the result one at a time. Furthermore, it lists
|
|
|
|
|
only files which were modified from all parents. `-c` implies
|
|
|
|
|
`-p`.
|
|
|
|
|
+
|
|
|
|
|
--diff-merges=dense-combined:::
|
|
|
|
|
--diff-merges=cc:::
|
|
|
|
|
--cc:::
|
|
|
|
|
With this option the output produced by
|
|
|
|
|
`--diff-merges=combined` is further compressed by omitting
|
|
|
|
|
uninteresting hunks whose contents in the parents have only
|
|
|
|
|
two variants and the merge result picks one of them without
|
|
|
|
|
modification. `--cc` implies `-p`.
|
|
|
|
|
|
|
|
|
|
--combined-all-paths::
|
|
|
|
|
This flag causes combined diffs (used for merge commits) to
|
|
|
|
|
list the name of the file from all parents. It thus only has
|
|
|
|
|
effect when `--diff-merges=[dense-]combined` is in use, and
|
|
|
|
|
is likely only useful if filename changes are detected (i.e.
|
|
|
|
|
when either rename or copy detection have been requested).
|
|
|
|
|
endif::git-log[]
|
|
|
|
|
|
2007-07-25 12:08:17 +02:00
|
|
|
-U<n>::
|
|
|
|
|
--unified=<n>::
|
|
|
|
|
Generate diffs with <n> lines of context instead of
|
2020-10-31 20:37:34 +01:00
|
|
|
the usual three.
|
2009-11-07 10:51:56 +01:00
|
|
|
ifndef::git-format-patch[]
|
2020-10-31 20:37:34 +01:00
|
|
|
Implies `--patch`.
|
2009-11-07 10:51:56 +01:00
|
|
|
endif::git-format-patch[]
|
2007-07-25 12:08:17 +02:00
|
|
|
|
2019-02-21 12:16:12 +01:00
|
|
|
--output=<file>::
|
|
|
|
|
Output to a specific file instead of stdout.
|
|
|
|
|
|
|
|
|
|
--output-indicator-new=<char>::
|
|
|
|
|
--output-indicator-old=<char>::
|
|
|
|
|
--output-indicator-context=<char>::
|
|
|
|
|
Specify the character used to indicate new, old or context
|
|
|
|
|
lines in the generated patch. Normally they are '+', '-' and
|
|
|
|
|
' ' respectively.
|
|
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
ifndef::git-format-patch[]
|
2006-07-07 14:28:05 +02:00
|
|
|
--raw::
|
2015-05-18 19:55:57 +02:00
|
|
|
ifndef::git-log[]
|
|
|
|
|
Generate the diff in raw format.
|
2015-05-14 06:34:48 +02:00
|
|
|
ifdef::git-diff-core[]
|
|
|
|
|
This is the default.
|
|
|
|
|
endif::git-diff-core[]
|
2015-05-18 19:55:57 +02:00
|
|
|
endif::git-log[]
|
|
|
|
|
ifdef::git-log[]
|
|
|
|
|
For each commit, show a summary of changes using the raw diff
|
|
|
|
|
format. See the "RAW OUTPUT FORMAT" section of
|
|
|
|
|
linkgit:git-diff[1]. This is different from showing the log
|
|
|
|
|
itself in raw format, which you can achieve with
|
|
|
|
|
`--format=raw`.
|
|
|
|
|
endif::git-log[]
|
2009-11-07 10:52:29 +01:00
|
|
|
endif::git-format-patch[]
|
2006-07-07 14:28:05 +02:00
|
|
|
|
2009-11-07 10:51:56 +01:00
|
|
|
ifndef::git-format-patch[]
|
2006-04-11 13:22:17 +02:00
|
|
|
--patch-with-raw::
|
2009-11-07 10:53:07 +01:00
|
|
|
Synonym for `-p --raw`.
|
2009-11-07 10:51:56 +01:00
|
|
|
endif::git-format-patch[]
|
2006-04-11 13:22:17 +02:00
|
|
|
|
2020-07-29 22:12:10 +02:00
|
|
|
ifdef::git-log[]
|
|
|
|
|
-t::
|
|
|
|
|
Show the tree objects in the diff output.
|
|
|
|
|
endif::git-log[]
|
|
|
|
|
|
2017-10-29 16:12:28 +01:00
|
|
|
--indent-heuristic::
|
2018-06-11 15:56:13 +02:00
|
|
|
Enable the heuristic that shifts diff hunk boundaries to make patches
|
2017-10-29 16:12:28 +01:00
|
|
|
easier to read. This is the default.
|
|
|
|
|
|
|
|
|
|
--no-indent-heuristic::
|
|
|
|
|
Disable the indent heuristic.
|
2016-06-10 19:58:55 +02:00
|
|
|
|
2011-10-02 06:56:28 +02:00
|
|
|
--minimal::
|
|
|
|
|
Spend extra time to make sure the smallest possible
|
|
|
|
|
diff is produced.
|
|
|
|
|
|
2009-01-25 13:20:22 +01:00
|
|
|
--patience::
|
2009-01-01 17:39:17 +01:00
|
|
|
Generate a diff using the "patience diff" algorithm.
|
|
|
|
|
|
2012-03-06 14:15:02 +01:00
|
|
|
--histogram::
|
|
|
|
|
Generate a diff using the "histogram diff" algorithm.
|
|
|
|
|
|
2017-11-27 20:47:47 +01:00
|
|
|
--anchored=<text>::
|
|
|
|
|
Generate a diff using the "anchored diff" algorithm.
|
|
|
|
|
+
|
|
|
|
|
This option may be specified more than once.
|
|
|
|
|
+
|
|
|
|
|
If a line exists in both the source and destination, exists only once,
|
|
|
|
|
and starts with this text, this algorithm attempts to prevent it from
|
|
|
|
|
appearing as a deletion or addition in the output. It uses the "patience
|
|
|
|
|
diff" algorithm internally.
|
|
|
|
|
|
2013-01-16 08:51:58 +01:00
|
|
|
--diff-algorithm={patience|minimal|histogram|myers}::
|
|
|
|
|
Choose a diff algorithm. The variants are as follows:
|
|
|
|
|
+
|
|
|
|
|
--
|
|
|
|
|
`default`, `myers`;;
|
|
|
|
|
The basic greedy diff algorithm. Currently, this is the default.
|
|
|
|
|
`minimal`;;
|
|
|
|
|
Spend extra time to make sure the smallest possible diff is
|
|
|
|
|
produced.
|
|
|
|
|
`patience`;;
|
|
|
|
|
Use "patience diff" algorithm when generating patches.
|
|
|
|
|
`histogram`;;
|
|
|
|
|
This algorithm extends the patience algorithm to "support
|
|
|
|
|
low-occurrence common elements".
|
|
|
|
|
--
|
|
|
|
|
+
|
2018-06-11 15:56:13 +02:00
|
|
|
For instance, if you configured the `diff.algorithm` variable to a
|
2013-01-16 08:51:58 +01:00
|
|
|
non-default value and want to use the default one, then you
|
|
|
|
|
have to use `--diff-algorithm=default` option.
|
|
|
|
|
|
2011-05-27 14:36:41 +02:00
|
|
|
--stat[=<width>[,<name-width>[,<count>]]]::
|
2012-03-01 13:26:43 +01:00
|
|
|
Generate a diffstat. By default, as much space as necessary
|
2012-03-01 13:26:46 +01:00
|
|
|
will be used for the filename part, and the rest for the graph
|
|
|
|
|
part. Maximum width defaults to terminal width, or 80 columns
|
2012-06-22 22:03:01 +02:00
|
|
|
if not connected to a terminal, and can be overridden by
|
2012-03-01 13:26:46 +01:00
|
|
|
`<width>`. The width of the filename part can be limited by
|
|
|
|
|
giving another width `<name-width>` after a comma. The width
|
|
|
|
|
of the graph part can be limited by using
|
|
|
|
|
`--stat-graph-width=<width>` (affects all commands generating
|
|
|
|
|
a stat graph) or by setting `diff.statGraphWidth=<width>`
|
|
|
|
|
(does not affect `git format-patch`).
|
2011-05-27 14:36:41 +02:00
|
|
|
By giving a third parameter `<count>`, you can limit the
|
2012-03-01 13:26:43 +01:00
|
|
|
output to the first `<count>` lines, followed by `...` if
|
|
|
|
|
there are more.
|
2011-05-27 14:36:42 +02:00
|
|
|
+
|
|
|
|
|
These parameters can also be set individually with `--stat-width=<width>`,
|
|
|
|
|
`--stat-name-width=<name-width>` and `--stat-count=<count>`.
|
2006-04-14 00:15:30 +02:00
|
|
|
|
2018-02-24 15:09:59 +01:00
|
|
|
--compact-summary::
|
|
|
|
|
Output a condensed summary of extended header information such
|
|
|
|
|
as file creations or deletions ("new" or "gone", optionally "+l"
|
|
|
|
|
if it's a symlink) and mode changes ("+x" or "-x" for adding
|
|
|
|
|
or removing executable bit respectively) in diffstat. The
|
2018-06-17 06:35:54 +02:00
|
|
|
information is put between the filename part and the graph
|
2018-02-24 15:09:59 +01:00
|
|
|
part. Implies `--stat`.
|
|
|
|
|
|
2006-10-12 12:01:00 +02:00
|
|
|
--numstat::
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-26 10:51:57 +02:00
|
|
|
Similar to `--stat`, but shows number of added and
|
2006-10-12 12:01:00 +02:00
|
|
|
deleted lines in decimal notation and pathname without
|
2006-12-26 09:15:26 +01:00
|
|
|
abbreviation, to make it more machine friendly. For
|
|
|
|
|
binary files, outputs two `-` instead of saying
|
|
|
|
|
`0 0`.
|
2006-10-12 12:01:00 +02:00
|
|
|
|
2006-12-15 05:15:44 +01:00
|
|
|
--shortstat::
|
2009-11-07 10:53:07 +01:00
|
|
|
Output only the last line of the `--stat` format containing total
|
2006-12-15 05:15:44 +01:00
|
|
|
number of modified files, as well as number of added and deleted
|
|
|
|
|
lines.
|
|
|
|
|
|
2019-02-21 12:16:03 +01:00
|
|
|
-X[<param1,param2,...>]::
|
2011-04-29 11:36:18 +02:00
|
|
|
--dirstat[=<param1,param2,...>]::
|
|
|
|
|
Output the distribution of relative amount of changes for each
|
|
|
|
|
sub-directory. The behavior of `--dirstat` can be customized by
|
|
|
|
|
passing it a comma separated list of parameters.
|
2011-04-29 11:36:19 +02:00
|
|
|
The defaults are controlled by the `diff.dirstat` configuration
|
|
|
|
|
variable (see linkgit:git-config[1]).
|
2011-04-29 11:36:18 +02:00
|
|
|
The following parameters are available:
|
2011-04-11 00:48:50 +02:00
|
|
|
+
|
2011-04-29 11:36:18 +02:00
|
|
|
--
|
|
|
|
|
`changes`;;
|
|
|
|
|
Compute the dirstat numbers by counting the lines that have been
|
|
|
|
|
removed from the source, or added to the destination. This ignores
|
|
|
|
|
the amount of pure code movements within a file. In other words,
|
|
|
|
|
rearranging lines in a file is not counted as much as other changes.
|
|
|
|
|
This is the default behavior when no parameter is given.
|
New --dirstat=lines mode, doing dirstat analysis based on diffstat
This patch adds an alternative implementation of show_dirstat(), called
show_dirstat_by_line(), which uses the more expensive diffstat analysis
(as opposed to show_dirstat()'s own (relatively inexpensive) analysis)
to derive the numbers from which the --dirstat output is computed.
The alternative implementation is controlled by the new "lines" parameter
to the --dirstat option (or the diff.dirstat config variable).
For binary files, the diffstat analysis counts bytes instead of lines,
so to prevent binary files from dominating the dirstat results, the
byte counts for binary files are divided by 64 before being compared to
their textual/line-based counterparts. This is a stupid and ugly - but
very cheap - heuristic.
In linux-2.6.git, running the three different --dirstat modes:
time git diff v2.6.20..v2.6.30 --dirstat=changes > /dev/null
vs.
time git diff v2.6.20..v2.6.30 --dirstat=lines > /dev/null
vs.
time git diff v2.6.20..v2.6.30 --dirstat=files > /dev/null
yields the following average runtimes on my machine:
- "changes" (default): ~6.0 s
- "lines": ~9.6 s
- "files": ~0.1 s
So, as expected, there's a considerable performance hit (~60%) by going
through the full diffstat analysis as compared to the default "changes"
analysis (obviously, "files" is much faster than both). As such, the
"lines" mode is probably only useful if you really need the --dirstat
numbers to be consistent with the numbers returned from the other
--*stat options.
The patch also includes documentation and tests for the new dirstat mode.
Improved-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Johan Herland <johan@herland.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-04-29 11:36:21 +02:00
|
|
|
`lines`;;
|
|
|
|
|
Compute the dirstat numbers by doing the regular line-based diff
|
|
|
|
|
analysis, and summing the removed/added line counts. (For binary
|
|
|
|
|
files, count 64-byte chunks instead, since binary files have no
|
|
|
|
|
natural concept of lines). This is a more expensive `--dirstat`
|
|
|
|
|
behavior than the `changes` behavior, but it does count rearranged
|
|
|
|
|
lines within a file as much as other changes. The resulting output
|
|
|
|
|
is consistent with what you get from the other `--*stat` options.
|
2011-04-29 11:36:18 +02:00
|
|
|
`files`;;
|
|
|
|
|
Compute the dirstat numbers by counting the number of files changed.
|
|
|
|
|
Each changed file counts equally in the dirstat analysis. This is
|
|
|
|
|
the computationally cheapest `--dirstat` behavior, since it does
|
|
|
|
|
not have to look at the file contents at all.
|
|
|
|
|
`cumulative`;;
|
|
|
|
|
Count changes in a child directory for the parent directory as well.
|
|
|
|
|
Note that when using `cumulative`, the sum of the percentages
|
|
|
|
|
reported may exceed 100%. The default (non-cumulative) behavior can
|
|
|
|
|
be specified with the `noncumulative` parameter.
|
|
|
|
|
<limit>;;
|
|
|
|
|
An integer parameter specifies a cut-off percent (3% by default).
|
|
|
|
|
Directories contributing less than this percentage of the changes
|
|
|
|
|
are not shown in the output.
|
|
|
|
|
--
|
|
|
|
|
+
|
|
|
|
|
Example: The following will count changed files, while ignoring
|
|
|
|
|
directories with less than 10% of the total amount of changed files,
|
|
|
|
|
and accumulating child directory counts in the parent directories:
|
|
|
|
|
`--dirstat=files,10,cumulative`.
|
2008-09-05 21:27:35 +02:00
|
|
|
|
2019-02-21 12:16:03 +01:00
|
|
|
--cumulative::
|
|
|
|
|
Synonym for --dirstat=cumulative
|
|
|
|
|
|
|
|
|
|
--dirstat-by-file[=<param1,param2>...]::
|
|
|
|
|
Synonym for --dirstat=files,param1,param2...
|
|
|
|
|
|
2006-05-14 14:13:49 +02:00
|
|
|
--summary::
|
|
|
|
|
Output a condensed summary of extended header information
|
|
|
|
|
such as creations, renames and mode changes.
|
|
|
|
|
|
2009-11-07 10:51:56 +01:00
|
|
|
ifndef::git-format-patch[]
|
2006-04-15 13:41:18 +02:00
|
|
|
--patch-with-stat::
|
2009-11-07 10:53:07 +01:00
|
|
|
Synonym for `-p --stat`.
|
2009-11-07 10:51:56 +01:00
|
|
|
endif::git-format-patch[]
|
2006-04-15 13:41:18 +02:00
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
ifndef::git-format-patch[]
|
2009-11-22 20:43:20 +01:00
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-z::
|
2009-11-23 08:40:24 +01:00
|
|
|
ifdef::git-log[]
|
|
|
|
|
Separate the commits with NULs instead of with new newlines.
|
|
|
|
|
+
|
|
|
|
|
Also, when `--raw` or `--numstat` has been given, do not munge
|
|
|
|
|
pathnames and use NULs as output field terminators.
|
|
|
|
|
endif::git-log[]
|
2009-11-22 20:43:20 +01:00
|
|
|
ifndef::git-log[]
|
2010-04-18 20:28:17 +02:00
|
|
|
When `--raw`, `--numstat`, `--name-only` or `--name-status` has been
|
|
|
|
|
given, do not munge pathnames and use NULs as output field terminators.
|
2009-11-23 08:40:24 +01:00
|
|
|
endif::git-log[]
|
2009-11-22 20:43:20 +01:00
|
|
|
+
|
2017-03-02 20:03:52 +01:00
|
|
|
Without this option, pathnames with "unusual" characters are quoted as
|
|
|
|
|
explained for the configuration variable `core.quotePath` (see
|
|
|
|
|
linkgit:git-config[1]).
|
2005-07-13 21:52:35 +02:00
|
|
|
|
|
|
|
|
--name-only::
|
2021-04-20 13:24:37 +02:00
|
|
|
Show only names of changed files. The file names are often encoded in UTF-8.
|
|
|
|
|
For more information see the discussion about encoding in the linkgit:git-log[1]
|
|
|
|
|
manual page.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2005-09-21 09:20:06 +02:00
|
|
|
--name-status::
|
2008-04-22 14:23:48 +02:00
|
|
|
Show only names and status of changed files. See the description
|
|
|
|
|
of the `--diff-filter` option on what the status letters mean.
|
2021-04-20 13:24:37 +02:00
|
|
|
Just like `--name-only` the file names are often encoded in UTF-8.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2009-10-19 14:38:32 +02:00
|
|
|
--submodule[=<format>]::
|
2016-09-01 01:27:25 +02:00
|
|
|
Specify how differences in submodules are shown. When specifying
|
|
|
|
|
`--submodule=short` the 'short' format is used. This format just
|
|
|
|
|
shows the names of the commits at the beginning and end of the range.
|
|
|
|
|
When `--submodule` or `--submodule=log` is specified, the 'log'
|
|
|
|
|
format is used. This format lists the commits in the range like
|
|
|
|
|
linkgit:git-submodule[1] `summary` does. When `--submodule=diff`
|
|
|
|
|
is specified, the 'diff' format is used. This format shows an
|
|
|
|
|
inline diff of the changes in the submodule contents between the
|
|
|
|
|
commit range. Defaults to `diff.submodule` or the 'short' format
|
|
|
|
|
if the config option is unset.
|
2009-10-19 14:38:32 +02:00
|
|
|
|
Add an optional argument for --color options
Make git-branch, git-show-branch, git-grep, and all the diff-based
programs accept an optional argument <when> for --color. The argument
is a colorbool: "always", "never", or "auto". If no argument is given,
"always" is used; --no-color is an alias for --color=never. This makes
the command-line interface consistent with other GNU tools, such as `ls'
and `grep', and with the git-config color options. Note that, without
an argument, --color and --no-color work exactly as before.
To implement this, two internal changes were made:
1. Allow the first argument of git_config_colorbool() to be NULL,
in which case it returns -1 if the argument isn't "always", "never",
or "auto".
2. Add OPT_COLOR_FLAG(), OPT__COLOR(), and parse_opt_color_flag_cb()
to the option parsing library. The callback uses
git_config_colorbool(), so color.h is now a dependency
of parse-options.c.
Signed-off-by: Mark Lodato <lodatom@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-17 05:55:58 +01:00
|
|
|
--color[=<when>]::
|
2006-07-07 14:28:05 +02:00
|
|
|
Show colored diff.
|
2013-02-23 07:24:10 +01:00
|
|
|
`--color` (i.e. without '=<when>') is the same as `--color=always`.
|
|
|
|
|
'<when>' can be one of `always`, `never`, or `auto`.
|
2011-04-27 09:38:27 +02:00
|
|
|
ifdef::git-diff[]
|
|
|
|
|
It can be changed by the `color.ui` and `color.diff`
|
|
|
|
|
configuration settings.
|
|
|
|
|
endif::git-diff[]
|
2006-07-07 14:28:05 +02:00
|
|
|
|
|
|
|
|
--no-color::
|
2011-04-27 09:38:27 +02:00
|
|
|
Turn off colored diff.
|
|
|
|
|
ifdef::git-diff[]
|
|
|
|
|
This can be used to override configuration settings.
|
|
|
|
|
endif::git-diff[]
|
|
|
|
|
It is the same as `--color=never`.
|
2006-07-07 14:28:05 +02:00
|
|
|
|
2017-06-30 22:53:10 +02:00
|
|
|
--color-moved[=<mode>]::
|
|
|
|
|
Moved lines of code are colored differently.
|
|
|
|
|
ifdef::git-diff[]
|
|
|
|
|
It can be changed by the `diff.colorMoved` configuration setting.
|
|
|
|
|
endif::git-diff[]
|
|
|
|
|
The <mode> defaults to 'no' if the option is not given
|
|
|
|
|
and to 'zebra' if the option with no mode is given.
|
|
|
|
|
The mode must be one of:
|
|
|
|
|
+
|
|
|
|
|
--
|
|
|
|
|
no::
|
|
|
|
|
Moved lines are not highlighted.
|
|
|
|
|
default::
|
|
|
|
|
Is a synonym for `zebra`. This may change to a more sensible mode
|
|
|
|
|
in the future.
|
|
|
|
|
plain::
|
|
|
|
|
Any line that is added in one location and was removed
|
|
|
|
|
in another location will be colored with 'color.diff.newMoved'.
|
|
|
|
|
Similarly 'color.diff.oldMoved' will be used for removed lines
|
|
|
|
|
that are added somewhere else in the diff. This mode picks up any
|
|
|
|
|
moved line, but it is not very useful in a review to determine
|
|
|
|
|
if a block of code was moved without permutation.
|
2018-07-17 01:05:39 +02:00
|
|
|
blocks::
|
2017-08-16 03:27:39 +02:00
|
|
|
Blocks of moved text of at least 20 alphanumeric characters
|
|
|
|
|
are detected greedily. The detected blocks are
|
2018-07-17 01:05:39 +02:00
|
|
|
painted using either the 'color.diff.{old,new}Moved' color.
|
|
|
|
|
Adjacent blocks cannot be told apart.
|
|
|
|
|
zebra::
|
|
|
|
|
Blocks of moved text are detected as in 'blocks' mode. The blocks
|
|
|
|
|
are painted using either the 'color.diff.{old,new}Moved' color or
|
2017-06-30 22:53:10 +02:00
|
|
|
'color.diff.{old,new}MovedAlternative'. The change between
|
2017-08-16 03:27:39 +02:00
|
|
|
the two colors indicates that a new block was detected.
|
2018-07-24 23:58:45 +02:00
|
|
|
dimmed-zebra::
|
2017-06-30 22:53:10 +02:00
|
|
|
Similar to 'zebra', but additional dimming of uninteresting parts
|
|
|
|
|
of moved code is performed. The bordering lines of two adjacent
|
|
|
|
|
blocks are considered interesting, the rest is uninteresting.
|
2018-07-24 23:58:45 +02:00
|
|
|
`dimmed_zebra` is a deprecated synonym.
|
2017-06-30 22:53:10 +02:00
|
|
|
--
|
|
|
|
|
|
2018-11-23 12:16:50 +01:00
|
|
|
--no-color-moved::
|
|
|
|
|
Turn off move detection. This can be used to override configuration
|
|
|
|
|
settings. It is the same as `--color-moved=no`.
|
|
|
|
|
|
2018-07-17 01:05:40 +02:00
|
|
|
--color-moved-ws=<modes>::
|
2018-11-23 12:16:51 +01:00
|
|
|
This configures how whitespace is ignored when performing the
|
2018-07-18 21:31:56 +02:00
|
|
|
move detection for `--color-moved`.
|
|
|
|
|
ifdef::git-diff[]
|
|
|
|
|
It can be set by the `diff.colorMovedWS` configuration setting.
|
|
|
|
|
endif::git-diff[]
|
|
|
|
|
These modes can be given as a comma separated list:
|
2018-07-17 01:05:40 +02:00
|
|
|
+
|
|
|
|
|
--
|
2018-11-23 12:16:52 +01:00
|
|
|
no::
|
|
|
|
|
Do not ignore whitespace when performing move detection.
|
2018-07-17 01:05:40 +02:00
|
|
|
ignore-space-at-eol::
|
|
|
|
|
Ignore changes in whitespace at EOL.
|
|
|
|
|
ignore-space-change::
|
|
|
|
|
Ignore changes in amount of whitespace. This ignores whitespace
|
|
|
|
|
at line end, and considers all other sequences of one or
|
|
|
|
|
more whitespace characters to be equivalent.
|
|
|
|
|
ignore-all-space::
|
|
|
|
|
Ignore whitespace when comparing lines. This ignores differences
|
|
|
|
|
even if one line has whitespace where the other line has none.
|
diff.c: add white space mode to move detection that allows indent changes
The option of --color-moved has proven to be useful as observed on the
mailing list. However when refactoring sometimes the indentation changes,
for example when partitioning a functions into smaller helper functions
the code usually mostly moved around except for a decrease in indentation.
To just review the moved code ignoring the change in indentation, a mode
to ignore spaces in the move detection as implemented in a previous patch
would be enough. However the whole move coloring as motivated in commit
2e2d5ac (diff.c: color moved lines differently, 2017-06-30), brought
up the notion of the reviewer being able to trust the move of a "block".
As there are languages such as python, which depend on proper relative
indentation for the control flow of the program, ignoring any white space
change in a block would not uphold the promises of 2e2d5ac that allows
reviewers to pay less attention to the inside of a block, as inside
the reviewer wants to assume the same program flow.
This new mode of white space ignorance will take this into account and will
only allow the same white space changes per line in each block. This patch
even allows only for the same change at the beginning of the lines.
As this is a white space mode, it is made exclusive to other white space
modes in the move detection.
This patch brings some challenges, related to the detection of blocks.
We need a wide net to catch the possible moved lines, but then need to
narrow down to check if the blocks are still intact. Consider this
example (ignoring block sizes):
- A
- B
- C
+ A
+ B
+ C
At the beginning of a block when checking if there is a counterpart
for A, we have to ignore all space changes. However at the following
lines we have to check if the indent change stayed the same.
Checking if the indentation change did stay the same, is done by computing
the indentation change by the difference in line length, and then assume
the change is only in the beginning of the longer line, the common tail
is the same. That is why the test contains lines like:
- <TAB> A
...
+ A <TAB>
...
As the first line starting a block is caught using a compare function that
ignores white spaces unlike the rest of the block, where the white space
delta is taken into account for the comparison, we also have to think about
the following situation:
- A
- B
- A
- B
+ A
+ B
+ A
+ B
When checking if the first A (both in the + and - lines) is a start of
a block, we have to check all 'A' and record all the white space deltas
such that we can find the example above to be just one block that is
indented.
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-18 21:31:55 +02:00
|
|
|
allow-indentation-change::
|
2018-11-23 12:16:51 +01:00
|
|
|
Initially ignore any whitespace in the move detection, then
|
diff.c: add white space mode to move detection that allows indent changes
The option of --color-moved has proven to be useful as observed on the
mailing list. However when refactoring sometimes the indentation changes,
for example when partitioning a functions into smaller helper functions
the code usually mostly moved around except for a decrease in indentation.
To just review the moved code ignoring the change in indentation, a mode
to ignore spaces in the move detection as implemented in a previous patch
would be enough. However the whole move coloring as motivated in commit
2e2d5ac (diff.c: color moved lines differently, 2017-06-30), brought
up the notion of the reviewer being able to trust the move of a "block".
As there are languages such as python, which depend on proper relative
indentation for the control flow of the program, ignoring any white space
change in a block would not uphold the promises of 2e2d5ac that allows
reviewers to pay less attention to the inside of a block, as inside
the reviewer wants to assume the same program flow.
This new mode of white space ignorance will take this into account and will
only allow the same white space changes per line in each block. This patch
even allows only for the same change at the beginning of the lines.
As this is a white space mode, it is made exclusive to other white space
modes in the move detection.
This patch brings some challenges, related to the detection of blocks.
We need a wide net to catch the possible moved lines, but then need to
narrow down to check if the blocks are still intact. Consider this
example (ignoring block sizes):
- A
- B
- C
+ A
+ B
+ C
At the beginning of a block when checking if there is a counterpart
for A, we have to ignore all space changes. However at the following
lines we have to check if the indent change stayed the same.
Checking if the indentation change did stay the same, is done by computing
the indentation change by the difference in line length, and then assume
the change is only in the beginning of the longer line, the common tail
is the same. That is why the test contains lines like:
- <TAB> A
...
+ A <TAB>
...
As the first line starting a block is caught using a compare function that
ignores white spaces unlike the rest of the block, where the white space
delta is taken into account for the comparison, we also have to think about
the following situation:
- A
- B
- A
- B
+ A
+ B
+ A
+ B
When checking if the first A (both in the + and - lines) is a start of
a block, we have to check all 'A' and record all the white space deltas
such that we can find the example above to be just one block that is
indented.
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-18 21:31:55 +02:00
|
|
|
group the moved code blocks only into a block if the change in
|
|
|
|
|
whitespace is the same per line. This is incompatible with the
|
|
|
|
|
other modes.
|
2018-07-17 01:05:40 +02:00
|
|
|
--
|
|
|
|
|
|
2018-11-23 12:16:52 +01:00
|
|
|
--no-color-moved-ws::
|
|
|
|
|
Do not ignore whitespace when performing move detection. This can be
|
|
|
|
|
used to override configuration settings. It is the same as
|
|
|
|
|
`--color-moved-ws=no`.
|
|
|
|
|
|
2010-04-14 17:59:06 +02:00
|
|
|
--word-diff[=<mode>]::
|
|
|
|
|
Show a word diff, using the <mode> to delimit changed words.
|
|
|
|
|
By default, words are delimited by whitespace; see
|
|
|
|
|
`--word-diff-regex` below. The <mode> defaults to 'plain', and
|
|
|
|
|
must be one of:
|
|
|
|
|
+
|
|
|
|
|
--
|
|
|
|
|
color::
|
|
|
|
|
Highlight changed words using only colors. Implies `--color`.
|
|
|
|
|
plain::
|
|
|
|
|
Show words as `[-removed-]` and `{+added+}`. Makes no
|
|
|
|
|
attempts to escape the delimiters if they appear in the input,
|
|
|
|
|
so the output may be ambiguous.
|
|
|
|
|
porcelain::
|
|
|
|
|
Use a special line-based format intended for script
|
|
|
|
|
consumption. Added/removed/unchanged runs are printed in the
|
|
|
|
|
usual unified diff format, starting with a `+`/`-`/` `
|
|
|
|
|
character at the beginning of the line and extending to the
|
|
|
|
|
end of the line. Newlines in the input are represented by a
|
|
|
|
|
tilde `~` on a line of its own.
|
|
|
|
|
none::
|
|
|
|
|
Disable word diff again.
|
|
|
|
|
--
|
|
|
|
|
+
|
|
|
|
|
Note that despite the name of the first mode, color is used to
|
|
|
|
|
highlight the changed parts in all modes if enabled.
|
|
|
|
|
|
|
|
|
|
--word-diff-regex=<regex>::
|
|
|
|
|
Use <regex> to decide what a word is, instead of considering
|
|
|
|
|
runs of non-whitespace to be a word. Also implies
|
|
|
|
|
`--word-diff` unless it was already enabled.
|
2009-01-17 17:29:45 +01:00
|
|
|
+
|
2010-04-14 17:59:06 +02:00
|
|
|
Every non-overlapping match of the
|
2009-01-17 17:29:47 +01:00
|
|
|
<regex> is considered a word. Anything between these matches is
|
|
|
|
|
considered whitespace and ignored(!) for the purposes of finding
|
|
|
|
|
differences. You may want to append `|[^[:space:]]` to your regular
|
|
|
|
|
expression to make sure that it matches all non-whitespace characters.
|
|
|
|
|
A match that contains a newline is silently truncated(!) at the
|
|
|
|
|
newline.
|
2009-01-17 17:29:48 +01:00
|
|
|
+
|
2015-11-20 14:36:14 +01:00
|
|
|
For example, `--word-diff-regex=.` will treat each character as a word
|
|
|
|
|
and, correspondingly, show differences character by character.
|
|
|
|
|
+
|
2009-01-21 04:46:57 +01:00
|
|
|
The regex can also be set via a diff driver or configuration option, see
|
2016-05-04 19:36:24 +02:00
|
|
|
linkgit:gitattributes[5] or linkgit:git-config[1]. Giving it explicitly
|
2009-01-21 04:46:57 +01:00
|
|
|
overrides any diff driver or configuration setting. Diff drivers
|
|
|
|
|
override configuration settings.
|
2010-04-14 17:59:06 +02:00
|
|
|
|
|
|
|
|
--color-words[=<regex>]::
|
|
|
|
|
Equivalent to `--word-diff=color` plus (if a regex was
|
|
|
|
|
specified) `--word-diff-regex=<regex>`.
|
2009-11-07 10:52:29 +01:00
|
|
|
endif::git-format-patch[]
|
2006-07-28 23:56:15 +02:00
|
|
|
|
2006-07-07 14:28:05 +02:00
|
|
|
--no-renames::
|
|
|
|
|
Turn off rename detection, even when the configuration
|
|
|
|
|
file gives the default to do so.
|
|
|
|
|
|
2019-02-21 12:16:18 +01:00
|
|
|
--[no-]rename-empty::
|
|
|
|
|
Whether to use empty blobs as rename source.
|
|
|
|
|
|
2009-11-07 10:51:56 +01:00
|
|
|
ifndef::git-format-patch[]
|
2007-01-27 14:21:53 +01:00
|
|
|
--check::
|
2016-03-29 20:59:45 +02:00
|
|
|
Warn if changes introduce conflict markers or whitespace errors.
|
|
|
|
|
What are considered whitespace errors is controlled by `core.whitespace`
|
2011-06-22 17:33:02 +02:00
|
|
|
configuration. By default, trailing whitespaces (including
|
2018-06-11 15:56:13 +02:00
|
|
|
lines that consist solely of whitespaces) and a space character
|
2011-06-22 17:33:02 +02:00
|
|
|
that is immediately followed by a tab character inside the
|
|
|
|
|
initial indent of the line are considered whitespace errors.
|
|
|
|
|
Exits with non-zero status if problems are found. Not compatible
|
|
|
|
|
with --exit-code.
|
2015-05-26 19:11:28 +02:00
|
|
|
|
|
|
|
|
--ws-error-highlight=<kind>::
|
2017-07-25 22:53:15 +02:00
|
|
|
Highlight whitespace errors in the `context`, `old` or `new`
|
|
|
|
|
lines of the diff. Multiple values are separated by comma,
|
|
|
|
|
`none` resets previous values, `default` reset the list to
|
|
|
|
|
`new` and `all` is a shorthand for `old,new,context`. When
|
|
|
|
|
this option is not given, and the configuration variable
|
|
|
|
|
`diff.wsErrorHighlight` is not set, only whitespace errors in
|
|
|
|
|
`new` lines are highlighted. The whitespace errors are colored
|
2018-06-11 15:56:13 +02:00
|
|
|
with `color.diff.whitespace`.
|
2015-05-26 19:11:28 +02:00
|
|
|
|
2009-11-07 10:51:56 +01:00
|
|
|
endif::git-format-patch[]
|
2007-01-27 14:21:53 +01:00
|
|
|
|
2005-11-15 02:53:22 +01:00
|
|
|
--full-index::
|
2008-07-02 09:49:59 +02:00
|
|
|
Instead of the first handful of characters, show the full
|
|
|
|
|
pre- and post-image blob object names on the "index"
|
|
|
|
|
line when generating patch format output.
|
2006-07-07 14:28:05 +02:00
|
|
|
|
|
|
|
|
--binary::
|
2009-11-07 10:53:07 +01:00
|
|
|
In addition to `--full-index`, output a binary diff that
|
2020-10-31 20:37:34 +01:00
|
|
|
can be applied with `git-apply`.
|
|
|
|
|
ifndef::git-format-patch[]
|
|
|
|
|
Implies `--patch`.
|
|
|
|
|
endif::git-format-patch[]
|
2005-11-15 02:53:22 +01:00
|
|
|
|
2005-12-18 11:03:15 +01:00
|
|
|
--abbrev[=<n>]::
|
2005-12-14 02:21:41 +01:00
|
|
|
Instead of showing the full 40-byte hexadecimal object
|
|
|
|
|
name in diff-raw format output and diff-tree header
|
2020-11-04 23:01:37 +01:00
|
|
|
lines, show the shortest prefix that is at least '<n>'
|
|
|
|
|
hexdigits long that uniquely refers the object.
|
diff: index-line: respect --abbrev in object's name
A handful of Git's commands respect `--abbrev' for customizing length
of abbreviation of object names.
For diff-family, Git supports 2 different options for 2 different
purposes, `--full-index' for showing diff-patch object's name in full,
and `--abbrev' to customize the length of object names in diff-raw and
diff-tree header lines, without any options to customise the length of
object names in diff-patch format. When working with diff-patch format,
we only have two options, either full index, or default abbrev length.
Although, that behaviour is documented, it doesn't stop users from
trying to use `--abbrev' with the hope of customising diff-patch's
objects' name's abbreviation.
Let's allow the blob object names shown on the "index" line to be
abbreviated to arbitrary length given via the "--abbrev" option.
To preserve backward compatibility with old script that specify both
`--full-index' and `--abbrev', always show full object id
if `--full-index' is specified.
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-08-21 13:51:47 +02:00
|
|
|
In diff-patch output format, `--full-index` takes higher
|
|
|
|
|
precedence, i.e. if `--full-index` is specified, full blob
|
|
|
|
|
names will be shown regardless of `--abbrev`.
|
|
|
|
|
Non default number of digits can be specified with `--abbrev=<n>`.
|
2005-12-14 02:21:41 +01:00
|
|
|
|
2010-08-05 18:14:25 +02:00
|
|
|
-B[<n>][/<m>]::
|
2010-09-28 01:58:26 +02:00
|
|
|
--break-rewrites[=[<n>][/<m>]]::
|
2010-08-05 18:14:25 +02:00
|
|
|
Break complete rewrite changes into pairs of delete and
|
|
|
|
|
create. This serves two purposes:
|
|
|
|
|
+
|
|
|
|
|
It affects the way a change that amounts to a total rewrite of a file
|
|
|
|
|
not as a series of deletion and insertion mixed together with a very
|
|
|
|
|
few lines that happen to match textually as the context, but as a
|
|
|
|
|
single deletion of everything old followed by a single insertion of
|
|
|
|
|
everything new, and the number `m` controls this aspect of the -B
|
|
|
|
|
option (defaults to 60%). `-B/70%` specifies that less than 30% of the
|
2013-01-21 20:17:53 +01:00
|
|
|
original should remain in the result for Git to consider it a total
|
2010-08-05 18:14:25 +02:00
|
|
|
rewrite (i.e. otherwise the resulting patch will be a series of
|
|
|
|
|
deletion and insertion mixed together with context lines).
|
|
|
|
|
+
|
|
|
|
|
When used with -M, a totally-rewritten file is also considered as the
|
|
|
|
|
source of a rename (usually -M only considers a file that disappeared
|
|
|
|
|
as the source of a rename), and the number `n` controls this aspect of
|
|
|
|
|
the -B option (defaults to 50%). `-B20%` specifies that a change with
|
|
|
|
|
addition and deletion compared to 20% or more of the file's size are
|
|
|
|
|
eligible for being picked up as a possible source of a rename to
|
|
|
|
|
another file.
|
|
|
|
|
|
|
|
|
|
-M[<n>]::
|
2010-11-10 21:27:12 +01:00
|
|
|
--find-renames[=<n>]::
|
2010-05-08 06:44:34 +02:00
|
|
|
ifndef::git-log[]
|
2005-07-13 21:52:35 +02:00
|
|
|
Detect renames.
|
2010-05-08 06:44:34 +02:00
|
|
|
endif::git-log[]
|
|
|
|
|
ifdef::git-log[]
|
|
|
|
|
If generating diffs, detect and report renames for each commit.
|
|
|
|
|
For following files across renames while traversing history, see
|
|
|
|
|
`--follow`.
|
|
|
|
|
endif::git-log[]
|
2011-05-06 06:16:17 +02:00
|
|
|
If `n` is specified, it is a threshold on the similarity
|
2010-08-05 18:14:25 +02:00
|
|
|
index (i.e. amount of addition/deletions compared to the
|
2013-01-21 20:17:53 +01:00
|
|
|
file's size). For example, `-M90%` means Git should consider a
|
2010-08-05 18:14:25 +02:00
|
|
|
delete/add pair to be a rename if more than 90% of the file
|
2012-12-18 11:47:09 +01:00
|
|
|
hasn't changed. Without a `%` sign, the number is to be read as
|
|
|
|
|
a fraction, with a decimal point before it. I.e., `-M5` becomes
|
|
|
|
|
0.5, and is thus the same as `-M50%`. Similarly, `-M05` is
|
|
|
|
|
the same as `-M5%`. To limit detection to exact renames, use
|
2013-07-05 10:42:17 +02:00
|
|
|
`-M100%`. The default similarity index is 50%.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2010-08-05 18:14:25 +02:00
|
|
|
-C[<n>]::
|
2010-11-10 21:27:12 +01:00
|
|
|
--find-copies[=<n>]::
|
2007-06-11 22:12:19 +02:00
|
|
|
Detect copies as well as renames. See also `--find-copies-harder`.
|
2010-08-05 18:14:25 +02:00
|
|
|
If `n` is specified, it has the same meaning as for `-M<n>`.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
|
|
|
|
--find-copies-harder::
|
2007-06-11 22:12:19 +02:00
|
|
|
For performance reasons, by default, `-C` option finds copies only
|
2007-06-07 09:04:01 +02:00
|
|
|
if the original file of the copy was modified in the same
|
2005-10-06 00:08:26 +02:00
|
|
|
changeset. This flag makes the command
|
2005-07-13 21:52:35 +02:00
|
|
|
inspect unmodified files as candidates for the source of
|
|
|
|
|
copy. This is a very expensive operation for large
|
2007-06-11 22:12:19 +02:00
|
|
|
projects, so use it with caution. Giving more than one
|
|
|
|
|
`-C` option has the same effect.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2011-03-01 01:11:55 +01:00
|
|
|
-D::
|
|
|
|
|
--irreversible-delete::
|
|
|
|
|
Omit the preimage for deletes, i.e. print only the header but not
|
|
|
|
|
the diff between the preimage and `/dev/null`. The resulting patch
|
2014-04-01 00:11:44 +02:00
|
|
|
is not meant to be applied with `patch` or `git apply`; this is
|
2011-03-01 01:11:55 +01:00
|
|
|
solely for people who want to just concentrate on reviewing the
|
2017-07-31 16:00:31 +02:00
|
|
|
text after the change. In addition, the output obviously lacks
|
2011-03-01 01:11:55 +01:00
|
|
|
enough information to apply such a patch in reverse, even manually,
|
|
|
|
|
hence the name of the option.
|
|
|
|
|
+
|
|
|
|
|
When used together with `-B`, omit also the preimage in the deletion part
|
|
|
|
|
of a delete/create pair.
|
|
|
|
|
|
2005-09-21 09:18:27 +02:00
|
|
|
-l<num>::
|
2021-07-15 02:45:22 +02:00
|
|
|
The `-M` and `-C` options involve some preliminary steps that
|
|
|
|
|
can detect subsets of renames/copies cheaply, followed by an
|
|
|
|
|
exhaustive fallback portion that compares all remaining
|
|
|
|
|
unpaired destinations to all relevant sources. (For renames,
|
|
|
|
|
only remaining unpaired sources are relevant; for copies, all
|
|
|
|
|
original sources are relevant.) For N sources and
|
|
|
|
|
destinations, this exhaustive check is O(N^2). This option
|
|
|
|
|
prevents the exhaustive portion of rename/copy detection from
|
|
|
|
|
running if the number of source/destination files involved
|
|
|
|
|
exceeds the specified number. Defaults to diff.renameLimit.
|
2021-07-15 02:45:23 +02:00
|
|
|
Note that a value of 0 is treated as unlimited.
|
2005-09-21 09:18:27 +02:00
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
ifndef::git-format-patch[]
|
2010-11-10 21:27:13 +01:00
|
|
|
--diff-filter=[(A|C|D|M|R|T|U|X|B)...[*]]::
|
|
|
|
|
Select only files that are Added (`A`), Copied (`C`),
|
|
|
|
|
Deleted (`D`), Modified (`M`), Renamed (`R`), have their
|
|
|
|
|
type (i.e. regular file, symlink, submodule, ...) changed (`T`),
|
|
|
|
|
are Unmerged (`U`), are
|
|
|
|
|
Unknown (`X`), or have had their pairing Broken (`B`).
|
|
|
|
|
Any combination of the filter characters (including none) can be used.
|
|
|
|
|
When `*` (All-or-none) is added to the combination, all
|
|
|
|
|
paths are selected if there is any file that matches
|
|
|
|
|
other criteria in the comparison; if there is no file
|
|
|
|
|
that matches other criteria, nothing is selected.
|
2016-07-14 21:17:47 +02:00
|
|
|
+
|
|
|
|
|
Also, these upper-case letters can be downcased to exclude. E.g.
|
|
|
|
|
`--diff-filter=ad` excludes added and deleted paths.
|
2018-01-04 17:49:42 +01:00
|
|
|
+
|
|
|
|
|
Note that not all diffs can feature all types. For instance, diffs
|
|
|
|
|
from the index to the working tree can never have Added entries
|
|
|
|
|
(because the set of paths included in the diff is limited by what is in
|
|
|
|
|
the index). Similarly, copied and renamed entries cannot appear if
|
|
|
|
|
detection for those types is disabled.
|
2010-11-10 21:27:13 +01:00
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-S<string>::
|
2013-05-31 14:12:15 +02:00
|
|
|
Look for differences that change the number of occurrences of
|
|
|
|
|
the specified string (i.e. addition/deletion) in a file.
|
|
|
|
|
Intended for the scripter's use.
|
|
|
|
|
+
|
|
|
|
|
It is useful when you're looking for an exact block of code (like a
|
|
|
|
|
struct), and want to know the history of that block since it first
|
|
|
|
|
came into being: use the feature iteratively to feed the interesting
|
|
|
|
|
block in the preimage back into `-S`, and keep going until you get the
|
|
|
|
|
very first version of the block.
|
2018-12-14 19:49:12 +01:00
|
|
|
+
|
|
|
|
|
Binary files are searched as well.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2010-08-23 19:17:03 +02:00
|
|
|
-G<regex>::
|
2013-05-31 14:12:15 +02:00
|
|
|
Look for differences whose patch text contains added/removed
|
|
|
|
|
lines that match <regex>.
|
|
|
|
|
+
|
|
|
|
|
To illustrate the difference between `-S<regex> --pickaxe-regex` and
|
|
|
|
|
`-G<regex>`, consider a commit with the following diff in the same
|
|
|
|
|
file:
|
|
|
|
|
+
|
|
|
|
|
----
|
2020-02-06 21:53:01 +01:00
|
|
|
+ return frotz(nitfol, two->ptr, 1, 0);
|
2013-05-31 14:12:15 +02:00
|
|
|
...
|
2020-02-06 21:53:01 +01:00
|
|
|
- hit = frotz(nitfol, mf2.ptr, 1, 0);
|
2013-05-31 14:12:15 +02:00
|
|
|
----
|
|
|
|
|
+
|
2020-02-06 21:53:01 +01:00
|
|
|
While `git log -G"frotz\(nitfol"` will show this commit, `git log
|
|
|
|
|
-S"frotz\(nitfol" --pickaxe-regex` will not (because the number of
|
2013-05-31 14:12:15 +02:00
|
|
|
occurrences of that string did not change).
|
|
|
|
|
+
|
2018-12-14 19:49:12 +01:00
|
|
|
Unless `--text` is supplied patches of binary files without a textconv
|
|
|
|
|
filter will be ignored.
|
|
|
|
|
+
|
2013-05-31 14:12:15 +02:00
|
|
|
See the 'pickaxe' entry in linkgit:gitdiffcore[7] for more
|
|
|
|
|
information.
|
2010-08-23 19:17:03 +02:00
|
|
|
|
2018-01-04 23:50:42 +01:00
|
|
|
--find-object=<object-id>::
|
|
|
|
|
Look for differences that change the number of occurrences of
|
|
|
|
|
the specified object. Similar to `-S`, just the argument is different
|
|
|
|
|
in that it doesn't search for a specific string but for a specific
|
|
|
|
|
object id.
|
|
|
|
|
+
|
|
|
|
|
The object can be a blob or a submodule commit. It implies the `-t` option in
|
|
|
|
|
`git-log` to also find trees.
|
|
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
--pickaxe-all::
|
2010-08-23 19:17:03 +02:00
|
|
|
When `-S` or `-G` finds a change, show all the changes in that
|
2005-10-06 00:08:26 +02:00
|
|
|
changeset, not just the files that contain the change
|
2005-07-13 21:52:35 +02:00
|
|
|
in <string>.
|
|
|
|
|
|
2006-03-29 02:16:33 +02:00
|
|
|
--pickaxe-regex::
|
2013-05-31 14:12:15 +02:00
|
|
|
Treat the <string> given to `-S` as an extended POSIX regular
|
|
|
|
|
expression to match.
|
2018-01-04 23:50:42 +01:00
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
endif::git-format-patch[]
|
2006-03-29 02:16:33 +02:00
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-O<orderfile>::
|
2017-01-15 23:16:31 +01:00
|
|
|
Control the order in which files appear in the output.
|
2015-03-11 21:32:45 +01:00
|
|
|
This overrides the `diff.orderFile` configuration variable
|
|
|
|
|
(see linkgit:git-config[1]). To cancel `diff.orderFile`,
|
2013-12-19 01:08:12 +01:00
|
|
|
use `-O/dev/null`.
|
2017-01-15 23:16:31 +01:00
|
|
|
+
|
|
|
|
|
The output order is determined by the order of glob patterns in
|
|
|
|
|
<orderfile>.
|
|
|
|
|
All files with pathnames that match the first pattern are output
|
|
|
|
|
first, all files with pathnames that match the second pattern (but not
|
|
|
|
|
the first) are output next, and so on.
|
|
|
|
|
All files with pathnames that do not match any pattern are output
|
|
|
|
|
last, as if there was an implicit match-all pattern at the end of the
|
|
|
|
|
file.
|
|
|
|
|
If multiple pathnames have the same rank (they match the same pattern
|
|
|
|
|
but no earlier patterns), their output order relative to each other is
|
|
|
|
|
the normal order.
|
|
|
|
|
+
|
|
|
|
|
<orderfile> is parsed as follows:
|
|
|
|
|
+
|
|
|
|
|
--
|
|
|
|
|
- Blank lines are ignored, so they can be used as separators for
|
|
|
|
|
readability.
|
|
|
|
|
|
|
|
|
|
- Lines starting with a hash ("`#`") are ignored, so they can be used
|
|
|
|
|
for comments. Add a backslash ("`\`") to the beginning of the
|
|
|
|
|
pattern if it starts with a hash.
|
|
|
|
|
|
|
|
|
|
- Each other line contains a single pattern.
|
|
|
|
|
--
|
|
|
|
|
+
|
|
|
|
|
Patterns have the same syntax and semantics as patterns used for
|
2018-04-05 19:20:26 +02:00
|
|
|
fnmatch(3) without the FNM_PATHNAME flag, except a pathname also
|
2017-01-15 23:16:31 +01:00
|
|
|
matches a pattern if removing any number of the final pathname
|
|
|
|
|
components matches the pattern. For example, the pattern "`foo*bar`"
|
|
|
|
|
matches "`fooasdfbar`" and "`foo/bar/baz/asdf`" but not "`foobarx`".
|
2005-07-13 21:52:35 +02:00
|
|
|
|
diff: --{rotate,skip}-to=<path>
In the implementation of "git difftool", there is a case where the
user wants to start viewing the diffs at a specific path and
continue on to the rest, optionally wrapping around to the
beginning. Since it is somewhat cumbersome to implement such a
feature as a post-processing step of "git diff" output, let's
support it internally with two new options.
- "git diff --rotate-to=C", when the resulting patch would show
paths A B C D E without the option, would "rotate" the paths to
shows patch to C D E A B instead. It is an error when there is
no patch for C is shown.
- "git diff --skip-to=C" would instead "skip" the paths before C,
and shows patch to C D E. Again, it is an error when there is no
patch for C is shown.
- "git log [-p]" also accepts these two options, but it is not an
error if there is no change to the specified path. Instead, the
set of output paths are rotated or skipped to the specified path
or the first path that sorts after the specified path.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-02-11 20:57:50 +01:00
|
|
|
--skip-to=<file>::
|
|
|
|
|
--rotate-to=<file>::
|
|
|
|
|
Discard the files before the named <file> from the output
|
|
|
|
|
(i.e. 'skip to'), or move them to the end of the output
|
|
|
|
|
(i.e. 'rotate to'). These were invented primarily for use
|
|
|
|
|
of the `git difftool` command, and may not be very useful
|
|
|
|
|
otherwise.
|
|
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
ifndef::git-format-patch[]
|
2005-07-13 21:52:35 +02:00
|
|
|
-R::
|
2005-11-11 02:12:27 +01:00
|
|
|
Swap two inputs; that is, show differences from index or
|
2005-07-13 21:52:35 +02:00
|
|
|
on-disk file to tree contents.
|
2020-05-22 12:46:18 +02:00
|
|
|
endif::git-format-patch[]
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2008-02-13 09:34:39 +01:00
|
|
|
--relative[=<path>]::
|
2020-05-22 12:46:18 +02:00
|
|
|
--no-relative::
|
diff --relative: output paths as relative to the current subdirectory
This adds --relative option to the diff family. When you start
from a subdirectory:
$ git diff --relative
shows only the diff that is inside your current subdirectory,
and without $prefix part. People who usually live in
subdirectories may like it.
There are a few things I should also mention about the change:
- This works not just with diff but also works with the log
family of commands, but the history pruning is not affected.
In other words, if you go to a subdirectory, you can say:
$ git log --relative -p
but it will show the log message even for commits that do not
touch the current directory. You can limit it by giving
pathspec yourself:
$ git log --relative -p .
This originally was not a conscious design choice, but we
have a way to affect diff pathspec and pruning pathspec
independently. IOW "git log --full-diff -p ." tells it to
prune history to commits that affect the current subdirectory
but show the changes with full context. I think it makes
more sense to leave pruning independent from --relative than
the obvious alternative of always pruning with the current
subdirectory, which would break the symmetry.
- Because this works also with the log family, you could
format-patch a single change, limiting the effect to your
subdirectory, like so:
$ cd gitk-git
$ git format-patch -1 --relative 911f1eb
But because that is a special purpose usage, this option will
never become the default, with or without repository or user
preference configuration. The risk of producing a partial
patch and sending it out by mistake is too great if we did
so.
- This is inherently incompatible with --no-index, which is a
bolted-on hack that does not have much to do with git
itself. I didn't bother checking and erroring out on the
combined use of the options, but probably I should.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-02-12 23:26:02 +01:00
|
|
|
When run from a subdirectory of the project, it can be
|
|
|
|
|
told to exclude changes outside the directory and show
|
2008-02-13 09:34:39 +01:00
|
|
|
pathnames relative to it with this option. When you are
|
|
|
|
|
not in a subdirectory (e.g. in a bare repository), you
|
|
|
|
|
can name which subdirectory to make the output relative
|
|
|
|
|
to by giving a <path> as an argument.
|
2020-05-22 12:46:18 +02:00
|
|
|
`--no-relative` can be used to countermand both `diff.relative` config
|
|
|
|
|
option and previous `--relative`.
|
diff --relative: output paths as relative to the current subdirectory
This adds --relative option to the diff family. When you start
from a subdirectory:
$ git diff --relative
shows only the diff that is inside your current subdirectory,
and without $prefix part. People who usually live in
subdirectories may like it.
There are a few things I should also mention about the change:
- This works not just with diff but also works with the log
family of commands, but the history pruning is not affected.
In other words, if you go to a subdirectory, you can say:
$ git log --relative -p
but it will show the log message even for commits that do not
touch the current directory. You can limit it by giving
pathspec yourself:
$ git log --relative -p .
This originally was not a conscious design choice, but we
have a way to affect diff pathspec and pruning pathspec
independently. IOW "git log --full-diff -p ." tells it to
prune history to commits that affect the current subdirectory
but show the changes with full context. I think it makes
more sense to leave pruning independent from --relative than
the obvious alternative of always pruning with the current
subdirectory, which would break the symmetry.
- Because this works also with the log family, you could
format-patch a single change, limiting the effect to your
subdirectory, like so:
$ cd gitk-git
$ git format-patch -1 --relative 911f1eb
But because that is a special purpose usage, this option will
never become the default, with or without repository or user
preference configuration. The risk of producing a partial
patch and sending it out by mistake is too great if we did
so.
- This is inherently incompatible with --no-index, which is a
bolted-on hack that does not have much to do with git
itself. I didn't bother checking and erroring out on the
combined use of the options, but probably I should.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-02-12 23:26:02 +01:00
|
|
|
|
2008-12-29 08:03:17 +01:00
|
|
|
-a::
|
2006-07-07 15:57:09 +02:00
|
|
|
--text::
|
|
|
|
|
Treat all files as text.
|
|
|
|
|
|
2017-10-26 08:32:27 +02:00
|
|
|
--ignore-cr-at-eol::
|
2018-04-05 19:20:26 +02:00
|
|
|
Ignore carriage-return at the end of line when doing a comparison.
|
2017-10-26 08:32:27 +02:00
|
|
|
|
2007-02-14 09:41:32 +01:00
|
|
|
--ignore-space-at-eol::
|
2007-12-12 09:12:01 +01:00
|
|
|
Ignore changes in whitespace at EOL.
|
2007-02-14 09:41:32 +01:00
|
|
|
|
2008-12-29 08:03:17 +01:00
|
|
|
-b::
|
2006-12-03 17:24:41 +01:00
|
|
|
--ignore-space-change::
|
2007-12-12 09:12:01 +01:00
|
|
|
Ignore changes in amount of whitespace. This ignores whitespace
|
|
|
|
|
at line end, and considers all other sequences of one or
|
|
|
|
|
more whitespace characters to be equivalent.
|
2006-12-03 17:24:41 +01:00
|
|
|
|
2008-12-29 08:03:17 +01:00
|
|
|
-w::
|
2006-12-03 17:24:41 +01:00
|
|
|
--ignore-all-space::
|
2007-12-12 09:12:01 +01:00
|
|
|
Ignore whitespace when comparing lines. This ignores
|
|
|
|
|
differences even if one line has whitespace where the other
|
2006-12-03 17:24:41 +01:00
|
|
|
line has none.
|
|
|
|
|
|
2013-06-19 20:46:07 +02:00
|
|
|
--ignore-blank-lines::
|
|
|
|
|
Ignore changes whose lines are all blank.
|
|
|
|
|
|
2020-10-20 08:48:09 +02:00
|
|
|
-I<regex>::
|
|
|
|
|
--ignore-matching-lines=<regex>::
|
|
|
|
|
Ignore changes whose all lines match <regex>. This option may
|
|
|
|
|
be specified more than once.
|
|
|
|
|
|
2008-12-28 19:45:32 +01:00
|
|
|
--inter-hunk-context=<lines>::
|
|
|
|
|
Show the context between diff hunks, up to the specified number
|
|
|
|
|
of lines, thereby fusing hunks that are close to each other.
|
2017-01-12 13:21:11 +01:00
|
|
|
Defaults to `diff.interHunkContext` or 0 if the config option
|
|
|
|
|
is unset.
|
2008-12-28 19:45:32 +01:00
|
|
|
|
2011-10-09 13:36:57 +02:00
|
|
|
-W::
|
|
|
|
|
--function-context::
|
2020-11-01 18:28:43 +01:00
|
|
|
Show whole function as context lines for each change.
|
|
|
|
|
The function names are determined in the same way as
|
|
|
|
|
`git diff` works out patch hunk headers (see 'Defining a
|
|
|
|
|
custom hunk-header' in linkgit:gitattributes[5]).
|
2011-10-09 13:36:57 +02:00
|
|
|
|
2009-11-07 10:52:29 +01:00
|
|
|
ifndef::git-format-patch[]
|
2011-11-08 22:29:30 +01:00
|
|
|
ifndef::git-log[]
|
2007-03-14 01:17:04 +01:00
|
|
|
--exit-code::
|
|
|
|
|
Make the program exit with codes similar to diff(1).
|
|
|
|
|
That is, it exits with 1 if there were differences and
|
|
|
|
|
0 means no differences.
|
|
|
|
|
|
2007-03-25 01:55:43 +01:00
|
|
|
--quiet::
|
2009-11-07 10:53:07 +01:00
|
|
|
Disable all output of the program. Implies `--exit-code`.
|
2011-11-08 22:29:30 +01:00
|
|
|
endif::git-log[]
|
2009-11-07 10:52:29 +01:00
|
|
|
endif::git-format-patch[]
|
2007-03-25 01:55:43 +01:00
|
|
|
|
2007-06-30 19:47:07 +02:00
|
|
|
--ext-diff::
|
|
|
|
|
Allow an external diff helper to be executed. If you set an
|
2007-12-29 07:20:38 +01:00
|
|
|
external diff driver with linkgit:gitattributes[5], you need
|
|
|
|
|
to use this option with linkgit:git-log[1] and friends.
|
2007-06-30 19:47:07 +02:00
|
|
|
|
|
|
|
|
--no-ext-diff::
|
|
|
|
|
Disallow external diff drivers.
|
|
|
|
|
|
2011-07-06 17:13:30 +02:00
|
|
|
--textconv::
|
|
|
|
|
--no-textconv::
|
|
|
|
|
Allow (or disallow) external text conversion filters to be run
|
|
|
|
|
when comparing binary files. See linkgit:gitattributes[5] for
|
|
|
|
|
details. Because textconv filters are typically a one-way
|
|
|
|
|
conversion, the resulting diff is suitable for human
|
|
|
|
|
consumption, but cannot be applied. For this reason, textconv
|
|
|
|
|
filters are enabled by default only for linkgit:git-diff[1] and
|
|
|
|
|
linkgit:git-log[1], but not for linkgit:git-format-patch[1] or
|
|
|
|
|
diff plumbing commands.
|
|
|
|
|
|
2010-06-08 18:31:51 +02:00
|
|
|
--ignore-submodules[=<when>]::
|
|
|
|
|
Ignore changes to submodules in the diff generation. <when> can be
|
2013-05-28 21:36:44 +02:00
|
|
|
either "none", "untracked", "dirty" or "all", which is the default.
|
2010-08-06 00:39:25 +02:00
|
|
|
Using "none" will consider the submodule modified when it either contains
|
|
|
|
|
untracked or modified files or its HEAD differs from the commit recorded
|
|
|
|
|
in the superproject and can be used to override any settings of the
|
2010-08-06 00:40:48 +02:00
|
|
|
'ignore' option in linkgit:git-config[1] or linkgit:gitmodules[5]. When
|
2010-06-08 18:31:51 +02:00
|
|
|
"untracked" is used submodules are not considered dirty when they only
|
|
|
|
|
contain untracked content (but they are still scanned for modified
|
|
|
|
|
content). Using "dirty" ignores all changes to the work tree of submodules,
|
|
|
|
|
only changes to the commits stored in the superproject are shown (this was
|
|
|
|
|
the behavior until 1.7.0). Using "all" hides all changes to submodules.
|
2008-05-14 19:03:31 +02:00
|
|
|
|
2007-12-18 20:32:14 +01:00
|
|
|
--src-prefix=<prefix>::
|
|
|
|
|
Show the given source prefix instead of "a/".
|
|
|
|
|
|
|
|
|
|
--dst-prefix=<prefix>::
|
|
|
|
|
Show the given destination prefix instead of "b/".
|
|
|
|
|
|
|
|
|
|
--no-prefix::
|
|
|
|
|
Do not show any source or destination prefix.
|
|
|
|
|
|
2016-09-01 01:27:20 +02:00
|
|
|
--line-prefix=<prefix>::
|
|
|
|
|
Prepend an additional prefix to every line of output.
|
|
|
|
|
|
2016-10-24 12:42:20 +02:00
|
|
|
--ita-invisible-in-index::
|
|
|
|
|
By default entries added by "git add -N" appear as an existing
|
|
|
|
|
empty file in "git diff" and a new file in "git diff --cached".
|
|
|
|
|
This option makes the entry appear as a new file in "git diff"
|
|
|
|
|
and non-existent in "git diff --cached". This option could be
|
|
|
|
|
reverted with `--ita-visible-in-index`. Both options are
|
|
|
|
|
experimental and could be removed in future.
|
|
|
|
|
|
2005-08-30 22:51:01 +02:00
|
|
|
For more detailed explanation on these common options, see also
|
2008-07-01 00:01:21 +02:00
|
|
|
linkgit:gitdiffcore[7].
|