From: "Sverre Rabbelier" <srabbelier@gmail.com>
To: "Wincent Colaiuta" <win@wincent.com>
Cc: devel@morey-chaisemartin.com,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Weird behaviour of git status
Date: Fri, 16 Jan 2009 14:17:20 +0100 [thread overview]
Message-ID: <bd6139dc0901160517ra26d69bw661816faaa91b339@mail.gmail.com> (raw)
In-Reply-To: <2A29AD77-2B8D-4491-92C1-62F5FFFBB00F@wincent.com>
On Fri, Jan 16, 2009 at 10:44, Wincent Colaiuta <win@wincent.com> wrote:
> "git status" shows you what would be committed if you ran "git commit" with
> the same parameters. So in your example, the output for "git status ." is
> exactly as you would expect.
>
> This is stated in the man page.
This is one of the first things I stumbled on when I started using
git. I often times wanted to do "git status -- pathspec" to see only
what changed in a certain directory, rather than what would be
committed if only the contents of that directory is committed.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-01-16 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 8:42 Weird behaviour of git status Nicolas Morey-Chaisemartin
2009-01-16 9:44 ` Wincent Colaiuta
2009-01-16 13:17 ` Sverre Rabbelier [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=bd6139dc0901160517ra26d69bw661816faaa91b339@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=devel@morey-chaisemartin.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.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).