From: "Ping Yin" <pkufranky@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Fwd: git diff-index --raw HEAD and git diff --raw HEAD output the same thing?
Date: Sun, 2 Mar 2008 13:22:52 +0800 [thread overview]
Message-ID: <46dff0320803012122r7e97f486m9e4970c81455cdf6@mail.gmail.com> (raw)
In-Reply-To: <46dff0320803010545n775f1441x579a53a8c07d0892@mail.gmail.com>
Sorry i have forgotten to cc git list
---------- Forwarded message ----------
From: Ping Yin <pkufranky@gmail.com>
Date: Sat, Mar 1, 2008 at 9:45 PM
Subject: Re: git diff-index --raw HEAD and git diff --raw HEAD output
the same thing?
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
On Sat, Mar 1, 2008 at 9:21 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> On Sat, 1 Mar 2008, Ping Yin wrote:
>
> > Strange things is this line
> > :160000 160000 34f279b1662a6bef6a8fdea1827bbdbd80f12444
> > 0000000000000000000000000000000000000000 M commonmake
> >
> > why mod is 160000 while sha1 is 0000...
>
> This indicates that a submodule (160000) was deleted (00000). It is
> easier not to handle a deletion as mode change...
>
No, it isn't deleted, git diff --raw HEAD shows the right result
And why do diff and diff-index show different result?
$ git status
# On branch master
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# deleted: WordBreak
# typechange: util
#
# Changed but not updated:
# (use "git add <file>..." to update what will be committed)
#
# modified: commonmake
> Ciao,
> Dscho
>
>
--
Ping Yin
next prev parent reply other threads:[~2008-03-02 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 13:10 git diff-index --raw HEAD and git diff --raw HEAD output the same thing? Ping Yin
2008-03-01 13:21 ` Johannes Schindelin
[not found] ` <46dff0320803010545n775f1441x579a53a8c07d0892@mail.gmail.com>
2008-03-02 5:22 ` Ping Yin [this message]
2008-03-02 5:48 ` Junio C Hamano
2008-03-02 6:07 ` Ping Yin
2008-03-02 5:24 ` Ping Yin
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=46dff0320803012122r7e97f486m9e4970c81455cdf6@mail.gmail.com \
--to=pkufranky@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.
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).