git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: jateeq <jawad_atiq@hotmail.com>
Cc: git@vger.kernel.org
Subject: Re: How do I get the correct modification status after running git diff?
Date: Thu, 04 Mar 2010 17:39:00 +0100	[thread overview]
Message-ID: <m2lje8avob.fsf@igel.home> (raw)
In-Reply-To: <27782895.post@talk.nabble.com> (jateeq's message of "Thu, 4 Mar 2010 08:11:13 -0800 (PST)")

jateeq <jawad_atiq@hotmail.com> writes:

> Renaming flie:
> mv randomfile.xml random.xml
>
> Diffing:
> git diff -M --name-status HEAD
>
> Output:
> D      randomfile.xml

random.xml is an untracked file, thus ignored.  You need to add -N it
first.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      parent reply	other threads:[~2010-03-04 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 15:40 How do I get the correct modification status after running git diff? jateeq
2010-03-04 16:11 ` jateeq
2010-03-04 16:34   ` Michael J Gruber
2010-03-04 16:39   ` Andreas Schwab [this message]

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=m2lje8avob.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=git@vger.kernel.org \
    --cc=jawad_atiq@hotmail.com \
    /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).