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::
|
|
|
|
Generate patches without diffstat.
|
|
|
|
endif::git-format-patch[]
|
|
|
|
|
|
|
|
ifndef::git-format-patch[]
|
2005-07-13 21:52:35 +02:00
|
|
|
-p::
|
2007-11-15 14:19:29 +01:00
|
|
|
Generate patch (see section on generating patches).
|
|
|
|
{git-diff? This is the default.}
|
|
|
|
endif::git-format-patch[]
|
2005-07-13 21:52:35 +02:00
|
|
|
|
|
|
|
-u::
|
|
|
|
Synonym for "-p".
|
|
|
|
|
2007-07-25 12:08:17 +02:00
|
|
|
-U<n>::
|
|
|
|
Shorthand for "--unified=<n>".
|
|
|
|
|
|
|
|
--unified=<n>::
|
|
|
|
Generate diffs with <n> lines of context instead of
|
|
|
|
the usual three. Implies "-p".
|
|
|
|
|
2006-07-07 14:28:05 +02:00
|
|
|
--raw::
|
|
|
|
Generate the raw format.
|
2007-11-15 14:19:29 +01:00
|
|
|
{git-diff-core? This is the default.}
|
2006-07-07 14:28:05 +02:00
|
|
|
|
2006-04-11 13:22:17 +02:00
|
|
|
--patch-with-raw::
|
2006-07-07 14:28:05 +02:00
|
|
|
Synonym for "-p --raw".
|
2006-04-11 13:22:17 +02:00
|
|
|
|
2006-09-29 00:07:16 +02:00
|
|
|
--stat[=width[,name-width]]::
|
|
|
|
Generate a diffstat. You can override the default
|
|
|
|
output width for 80-column terminal by "--stat=width".
|
|
|
|
The width of the filename part can be controlled by
|
|
|
|
giving another width to it separated by a comma.
|
2006-04-14 00:15:30 +02:00
|
|
|
|
2006-10-12 12:01:00 +02:00
|
|
|
--numstat::
|
|
|
|
Similar to \--stat, but shows number of added and
|
|
|
|
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::
|
|
|
|
Output only the last line of the --stat format containing total
|
|
|
|
number of modified files, as well as number of added and deleted
|
|
|
|
lines.
|
|
|
|
|
2008-04-21 20:15:52 +02:00
|
|
|
--dirstat[=limit]::
|
2008-09-01 02:50:28 +02:00
|
|
|
Output the distribution of relative amount of changes (number of lines added or
|
|
|
|
removed) for each sub-directory. Directories with changes below
|
|
|
|
a cut-off percent (3% by default) are not shown. The cut-off percent
|
|
|
|
can be set with "--dirstat=limit". Changes in a child directory is not
|
|
|
|
counted for the parent directory, unless "--cumulative" is used.
|
2008-04-21 20:15:52 +02:00
|
|
|
|
2006-05-14 14:13:49 +02:00
|
|
|
--summary::
|
|
|
|
Output a condensed summary of extended header information
|
|
|
|
such as creations, renames and mode changes.
|
|
|
|
|
2006-04-15 13:41:18 +02:00
|
|
|
--patch-with-stat::
|
2006-07-07 14:28:05 +02:00
|
|
|
Synonym for "-p --stat".
|
2007-11-15 14:19:29 +01:00
|
|
|
{git-format-patch? This is the default.}
|
2006-04-15 13:41:18 +02:00
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-z::
|
2007-07-26 08:45:42 +02:00
|
|
|
NUL-line termination on output. This affects the --raw
|
|
|
|
output field terminator. Also output from commands such
|
|
|
|
as "git-log" will be delimited with NUL between commits.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
|
|
|
--name-only::
|
|
|
|
Show only names of changed files.
|
|
|
|
|
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.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2006-07-07 14:28:05 +02:00
|
|
|
--color::
|
|
|
|
Show colored diff.
|
|
|
|
|
|
|
|
--no-color::
|
|
|
|
Turn off colored diff, even when the configuration file
|
|
|
|
gives the default to color output.
|
|
|
|
|
2006-07-28 23:56:15 +02:00
|
|
|
--color-words::
|
|
|
|
Show colored word diff, i.e. color words which have changed.
|
|
|
|
|
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.
|
|
|
|
|
2007-01-27 14:21:53 +01:00
|
|
|
--check::
|
|
|
|
Warn if changes introduce trailing whitespace
|
2007-12-13 21:24:52 +01:00
|
|
|
or an indent that uses a space before a tab. Exits with
|
|
|
|
non-zero status if problems are found. Not compatible with
|
|
|
|
--exit-code.
|
2007-01-27 14:21:53 +01:00
|
|
|
|
2005-11-15 02:53:22 +01:00
|
|
|
--full-index::
|
|
|
|
Instead of the first handful characters, show full
|
|
|
|
object name of pre- and post-image blob on the "index"
|
2006-07-07 14:28:05 +02:00
|
|
|
line when generating a patch format output.
|
|
|
|
|
|
|
|
--binary::
|
|
|
|
In addition to --full-index, output "binary diff" that
|
|
|
|
can be applied with "git apply".
|
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
|
2005-12-29 10:20:06 +01:00
|
|
|
lines, show only handful hexdigits prefix. This is
|
2005-12-18 11:03:15 +01:00
|
|
|
independent of --full-index option above, which controls
|
|
|
|
the diff-patch output format. Non default number of
|
|
|
|
digits can be specified with --abbrev=<n>.
|
2005-12-14 02:21:41 +01:00
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-B::
|
|
|
|
Break complete rewrite changes into pairs of delete and create.
|
|
|
|
|
|
|
|
-M::
|
|
|
|
Detect renames.
|
|
|
|
|
|
|
|
-C::
|
2007-06-11 22:12:19 +02:00
|
|
|
Detect copies as well as renames. See also `--find-copies-harder`.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
2006-02-09 16:12:11 +01:00
|
|
|
--diff-filter=[ACDMRTUXB*]::
|
|
|
|
Select only files that are Added (`A`), Copied (`C`),
|
|
|
|
Deleted (`D`), Modified (`M`), Renamed (`R`), have their
|
2008-10-18 17:20:51 +02:00
|
|
|
type (i.e. regular file, symlink, submodule, ...) changed (`T`),
|
|
|
|
are Unmerged (`U`), are
|
2006-02-09 16:12:11 +01:00
|
|
|
Unknown (`X`), or have had their pairing Broken (`B`).
|
|
|
|
Any combination of the filter characters may 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.
|
|
|
|
|
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
|
|
|
|
2005-09-21 09:18:27 +02:00
|
|
|
-l<num>::
|
|
|
|
-M and -C options require O(n^2) processing time where n
|
2005-10-06 00:08:26 +02:00
|
|
|
is the number of potential rename/copy targets. This
|
2005-09-21 09:18:27 +02:00
|
|
|
option prevents rename/copy detection from running if
|
2005-10-06 00:08:26 +02:00
|
|
|
the number of rename/copy targets exceeds the specified
|
2005-09-21 09:18:27 +02:00
|
|
|
number.
|
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-S<string>::
|
2005-10-06 00:08:26 +02:00
|
|
|
Look for differences that contain the change in <string>.
|
2005-07-13 21:52:35 +02:00
|
|
|
|
|
|
|
--pickaxe-all::
|
|
|
|
When -S 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::
|
|
|
|
Make the <string> not a plain string but an extended POSIX
|
|
|
|
regex to match.
|
|
|
|
|
2005-07-13 21:52:35 +02:00
|
|
|
-O<orderfile>::
|
|
|
|
Output the patch in the order specified in the
|
|
|
|
<orderfile>, which has one shell glob pattern per line.
|
|
|
|
|
|
|
|
-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.
|
|
|
|
|
2008-02-13 09:34:39 +01:00
|
|
|
--relative[=<path>]::
|
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.
|
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
|
|
|
|
2006-07-07 15:57:09 +02:00
|
|
|
--text::
|
|
|
|
Treat all files as text.
|
|
|
|
|
|
|
|
-a::
|
|
|
|
Shorthand for "--text".
|
|
|
|
|
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
|
|
|
|
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
|
|
|
|
|
|
|
-b::
|
|
|
|
Shorthand for "--ignore-space-change".
|
|
|
|
|
|
|
|
--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.
|
|
|
|
|
|
|
|
-w::
|
|
|
|
Shorthand for "--ignore-all-space".
|
|
|
|
|
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::
|
|
|
|
Disable all output of the program. Implies --exit-code.
|
|
|
|
|
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.
|
|
|
|
|
2008-05-14 19:03:31 +02:00
|
|
|
--ignore-submodules::
|
|
|
|
Ignore changes to submodules in the diff generation.
|
|
|
|
|
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.
|
|
|
|
|
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].
|