From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Subject: git diff --name-status does not always list changed files
Date: Thu, 28 Feb 2008 15:47:14 +0100 [thread overview]
Message-ID: <fq6hhi$cub$1@ger.gmane.org> (raw)
Hi,
I was getting a lot of "no newline at end of file" warnings with GCC, so
I decided to fix these files in my clean working tree with
for i in `find . -iname "*.c" -o -iname "*.cc" -o -iname "*.cpp" -o
-iname "*.h" -o -iname "*.hpp"`; do
echo $i
echo wq | ed $i > /dev/null 2>&1
done
Afterwards, I wanted so see a list of files that were actually affected,
but to my wonderment "git diff --name-status" did not list any files,
although both "git diff" and "gitk" showed the diffs correctly.
Is this a bug in "--name-status" that is does not detected changes if
only a final newline has been added, or am I missing something?
Thanks.
--
Sebastian Schuberth
next reply other threads:[~2008-02-28 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 14:47 Sebastian Schuberth [this message]
2008-02-28 19:33 ` git diff --name-status does not always list changed files Junio C Hamano
2008-02-28 21:23 ` Sebastian Schuberth
2008-02-28 21:42 ` Junio C Hamano
2008-02-28 22:19 ` Sebastian Schuberth
2008-02-28 22:51 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fq6hhi$cub$1@ger.gmane.org' \
--to=sschuberth@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).