Skip to contentSkip to conversation

Git diff does not detect newly added files to working tree

DISCUSSION jateeq 2 participants 2 messages Jun 15, 2016

lore
Share & tools
lore

jateeq

author
#0 lore raw

Hello,

If I add a new file to a working tree, and run the following command without having staged or committed the file, according to the manual I should be able to get the name of the file - but it just doesn't show up. Anyone knows what I'm doing wrong? Note that the added file is not empty.

Command: git diff --name-only --diff-filter=[ACDM*]
The manual is http://www.kernel.org/pub/software/scm/git/docs/git-diff.html
here .

Fanks,
Jawad

Signature · 2 lines
View this message in context: http://old.nabble.com/Git-diff-does-not-detect-newly-added-files-to-working-tree-tp27772711p27772711.html
Sent from the git mailing list archive at Nabble.com.
#1 lore raw
Quoted 5 lines · jateeq

Hello,

If I add a new file to a working tree, and run the following command without having staged or committed the file, according to the manual I should be able to get the name of the file

Which part of the manual makes you think you should see untracked files? (that's a real question ;-) ).

Quoted 1 line

- but it just doesn't show up. Anyone knows what I'm doing wrong?

git diff doesn't mention untracked files, but shows the diff between the working tree and the staged content for files known to git.

To see the files in "git diff", you have to let Git know about these files, with "git add --intent-to-add the-file-you-want-to-see" (alias "git add -N"), or you should use "git status".

Signature · 2 lines
Matthieu Moy
http://www-verimag.imag.fr/~moy/