From: jateeq <jawad_atiq@hotmail.com>
To: git@vger.kernel.org
Subject: Git diff does not detect newly added files to working tree
Date: Wed, 3 Mar 2010 12:03:48 -0800 (PST) [thread overview]
Message-ID: <27772711.post@talk.nabble.com> (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
--
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.
next reply other threads:[~2010-03-03 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 20:03 jateeq [this message]
2010-03-03 20:12 ` Git diff does not detect newly added files to working tree Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27772711.post@talk.nabble.com \
--to=jawad_atiq@hotmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).