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 …

DESCRIPTION Compares the files in the working tree and the index. When paths are specified, compares only those named paths. Otherwise all entries in the index are compared. The …

The "git-diff-tree" command begins its output by printing the hash of what is being compared. After that, all the commands print one output line per changed file.

This format lists the commits in the range like git-submodule [1] summary does. Omitting the --submodule option or specifying --submodule=short, uses the short format.

Par défaut, une entrée ajoutée par git add -N apparaît comme un fichier vide existant dans git diff et un nouveau fichier dans git diff --cached. Cette option fait apparaître l’entrée comme un …

When "git-diff-index", "git-diff-tree", or "git-diff-files" are run with a -p option, "git diff" without the --raw option, or "git log" with the "-p" option, they do not produce the output described above; …

Newer git diff output has embedded index information for each blob to help identify the original version that the patch applies to. When this flag is given, and if the original versions of the …

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-tree“, „git-diff-files“ und „git-diff --raw“ können die Option -c oder --cc benutzen, um Diff-Ausgaben auch für Merge-Commits zu erzeugen.

When shown by git diff-files -c, it compares the two unresolved merge parents with the working tree file (i.e. file1 is stage 2 aka "our version", file2 is stage 3 aka "their version").