All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Yubao <yubao.liu@gmail.com>
To: git@vger.kernel.org
Subject: problems of git-status
Date: Wed, 28 Mar 2007 15:59:16 +0800	[thread overview]
Message-ID: <460A2054.20404@gmail.com> (raw)

Hi,
   I find "git status" and "git status ." have different output and the latter
will go wrong in the case below:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
#!/bin/sh
rm -rf tt; mkdir tt; cd tt

git init
mkdir AA
echo hello>a
git add .
echo world>a

echo "different output..."
echo "--------------------git status-------------"
git status
echo "--------------------git status . ----------"
git status .

git add a
git commit -m "test"
echo hello world>a
git add a
sleep 4
echo world hello>a
echo "--------------------git status-------------"
git status
echo "--------------------git status . ----------"
git status .

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I use git version 1.5.1.rc2.15.g465b3, "git repo-config -l" shows:
	core.filemode=false
	core.logallrefupdates=true
	core.compression=9
	diff.color=auto
	pack.window=64
	merge.summary=true
	core.repositoryformatversion=0
	core.filemode=false
	core.bare=false


Here is the output of that script:

Initialized empty Git repository in .git/
different output...
--------------------git status-------------
# On branch master
#
# Initial commit
#
# Changes to be committed:
#   (use "git rm --cached <file>..." to unstage)
#
#	new file: a
#
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#
#	modified:   a
#
--------------------git status . ----------
# On branch master
#
# Initial commit
#
# Changes to be committed:
#   (use "git rm --cached <file>..." to unstage)
#
#	new file: a
#
Created initial commit dc57cb444335e73ce3320c1e368765b1a92e3be5
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 a
--------------------git status-------------
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#	modified:   a
#
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#
#	modified:   a
#
--------------------git status . ----------
fatal: Entry 'a' not uptodate. Cannot merge.

             reply	other threads:[~2007-03-28  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28  7:59 Liu Yubao [this message]
2007-03-28  8:57 ` problems of git-status 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460A2054.20404@gmail.com \
    --to=yubao.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.