|
|
|
git-diff-files(1)
|
|
|
|
=================
|
|
|
|
v0.1, May 2005
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
git-diff-files - Compares files in the working tree and the cache
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
|
|
|
'git-diff-files' [-p] [-q] [-r] [-z] [-R] [-B] [-M] [-C] [--find-copies-harder] [-O<orderfile>] [-S<string>] [--pickaxe-all] [<path>...]
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
|
|
|
Compares the files in the working tree and the cache. When paths
|
|
|
|
are specified, compares only those named paths. Otherwise all
|
|
|
|
entries in the cache are compared. The output format is the
|
|
|
|
same as "git-diff-cache" and "git-diff-tree".
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
-------
|
|
|
|
-p::
|
|
|
|
generate patch (see section on generating patches).
|
|
|
|
|
|
|
|
-q::
|
|
|
|
Remain silent even on nonexisting files
|
|
|
|
|
|
|
|
-R::
|
|
|
|
Swap two inputs; that is, show differences from on-disk files
|
|
|
|
to cache contents.
|
|
|
|
|
[PATCH] Add -B flag to diff-* brothers.
A new diffcore transformation, diffcore-break.c, is introduced.
When the -B flag is given, a patch that represents a complete
rewrite is broken into a deletion followed by a creation. This
makes it easier to review such a complete rewrite patch.
The -B flag takes the same syntax as the -M and -C flags to
specify the minimum amount of non-source material the resulting
file needs to have to be considered a complete rewrite, and
defaults to 99% if not specified.
As the new test t4008-diff-break-rewrite.sh demonstrates, if a
file is a complete rewrite, it is broken into a delete/create
pair, which can further be subjected to the usual rename
detection if -M or -C is used. For example, if file0 gets
completely rewritten to make it as if it were rather based on
file1 which itself disappeared, the following happens:
The original change looks like this:
file0 --> file0' (quite different from file0)
file1 --> /dev/null
After diffcore-break runs, it would become this:
file0 --> /dev/null
/dev/null --> file0'
file1 --> /dev/null
Then diffcore-rename matches them up:
file1 --> file0'
The internal score values are finer grained now. Earlier
maximum of 10000 has been raised to 60000; there is no user
visible changes but there is no reason to waste available bits.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
20 years ago
|
|
|
-B::
|
|
|
|
Break complete rewrite changes into pairs of delete and create.
|
|
|
|
|
|
|
|
-M::
|
|
|
|
Detect renames.
|
|
|
|
|
|
|
|
-C::
|
|
|
|
Detect copies as well as renames.
|
|
|
|
|
|
|
|
--find-copies-harder::
|
|
|
|
By default, -C option finds copies only if the original
|
|
|
|
file of the copy was modified in the same changeset for
|
|
|
|
performance reasons. This flag makes the command
|
|
|
|
inspect unmodified files as candidates for the source of
|
|
|
|
copy. This is a very expensive operation for large
|
|
|
|
projects, so use it with caution.
|
|
|
|
|
|
|
|
-S<string>::
|
|
|
|
Look for differences that contains the change in <string>.
|
|
|
|
|
|
|
|
--pickaxe-all::
|
|
|
|
When -S finds a change, show all the changes in that
|
|
|
|
changeset, not just the files that contains the change
|
|
|
|
in <string>.
|
|
|
|
|
|
|
|
-O<orderfile>::
|
|
|
|
Output the patch in the order specified in the
|
|
|
|
<orderfile>, which has one shell glob pattern per line.
|
|
|
|
|
|
|
|
-r::
|
|
|
|
This flag does not mean anything. It is there only to match
|
|
|
|
git-diff-tree. Unlike git-diff-tree, git-diff-files always looks
|
|
|
|
at all the subdirectories.
|
|
|
|
|
|
|
|
|
|
|
|
Output format
|
|
|
|
-------------
|
|
|
|
include::diff-format.txt[]
|
|
|
|
|
|
|
|
|
|
|
|
Author
|
|
|
|
------
|
|
|
|
Written by Linus Torvalds <torvalds@osdl.org>
|
|
|
|
|
|
|
|
Documentation
|
|
|
|
--------------
|
|
|
|
Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
|
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
|
|
|
Part of the link:git.html[git] suite
|
|
|
|
|