From: Junio C Hamano <junkio@cox.net>
To: Liu Yubao <yubao.liu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: problems of git-status
Date: Wed, 28 Mar 2007 01:57:46 -0700 [thread overview]
Message-ID: <7vy7lhkanp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <460A2054.20404@gmail.com> (Liu Yubao's message of "Wed, 28 Mar 2007 15:59:16 +0800")
Liu Yubao <yubao.liu@gmail.com> writes:
> I find "git status" and "git status ." have different output.
Think of "git status $ANY_ARGUMENTS" a preview of "git commit
$ANY_ARGUMENTS". If you have local modifications, "git commit"
and "git commit ." would do different things, so corresponding
"git status" should give you different output.
By giving "." to git status, the latter form is asking what
reminder message you would see in the commit log message buffer
if you say "git commit ."
prev parent reply other threads:[~2007-03-28 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 7:59 problems of git-status Liu Yubao
2007-03-28 8:57 ` Junio C Hamano [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=7vy7lhkanp.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=yubao.liu@gmail.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