From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH 0/6] "git commit --dry-run" updates
Date: Mon, 17 Aug 2009 12:01:41 +0200 [thread overview]
Message-ID: <200908171201.43343.trast@student.ethz.ch> (raw)
In-Reply-To: <1250330803-22171-1-git-send-email-gitster@pobox.com>
Junio C Hamano wrote:
> The third and the fourth ones tentatively introduce "git stat". The
> former is an incomplete implementation that ignores the pathspec, and the
> latter adds pathspec limiting to it. In the final form before it goes to
> 'next', these two should probably be squashed.
If it's not too much work, it would be nice to somehow detect if -u
can have any influence at all. For example,
$ git status bar
# Not currently on any branch.
nothing to commit (use -u to show untracked files)
is a bit misleading if 'bar' is tracked because adding a -u won't make
any difference.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-08-17 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 10:06 [PATCH 0/6] "git commit --dry-run" updates Junio C Hamano
2009-08-15 10:06 ` [PATCH 1/6] Documentation/git-commit.txt: describe --dry-run Junio C Hamano
2009-08-15 10:06 ` [PATCH 2/6] git commit --dry-run -v: show diff in color when asked Junio C Hamano
2009-08-15 10:06 ` [PATCH 3/6] git stat: the beginning Junio C Hamano
2009-08-15 10:06 ` [PATCH 4/6] git stat: pathspec limits, unlike traditional "git status" Junio C Hamano
2009-08-15 10:06 ` [PATCH 5/6] git stat -s: short status output Junio C Hamano
2009-08-15 10:06 ` [PATCH 6/6] git status: not "commit --dry-run" anymore Junio C Hamano
2009-08-17 10:01 ` Thomas Rast [this message]
2009-08-17 15:57 ` [PATCH 0/6] "git commit --dry-run" updates Junio C Hamano
2009-08-17 19:16 ` Thomas Rast
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=200908171201.43343.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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