From: Jeff King <peff@peff.net>
To: Wincent Colaiuta <win@wincent.com>
Cc: Kevin Ballard <kevin@sb.org>, Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: To page or not to page
Date: Fri, 2 May 2008 08:36:56 -0400 [thread overview]
Message-ID: <20080502123656.GA2680@sigill.intra.peff.net> (raw)
In-Reply-To: <807E185B-BEE5-4AAF-8DF4-EE597681D61C@wincent.com>
On Fri, May 02, 2008 at 12:34:10PM +0200, Wincent Colaiuta wrote:
> But evidently given that there has been so much backlash against the
> patch the only way to keep everyone happy will be to make this
> configurable.
Agreed.
But I wonder why there seems to be such a split between people who
clearly have short git-status output, and those who have long git-status
output.
I keep my "untracked files" list tidy. IOW, I always get:
$ git status
# On branch master
nothing to commit (working directory clean)
and if I don't, then I should be taking some action to commit things,
clean them up, or add them to my .git/info/exclude file. Do other people
generally carry around a lot of cruft that "git status" reports?
-Peff
next prev parent reply other threads:[~2008-05-02 12:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 5:41 To page or not to page Kevin Ballard
2008-05-02 5:45 ` Jeff King
2008-05-02 5:56 ` Junio C Hamano
2008-05-02 6:04 ` Kevin Ballard
2008-05-02 6:08 ` Junio C Hamano
2008-05-02 13:47 ` Bart Trojanowski
2008-05-02 9:41 ` Pedro Melo
2008-05-02 16:58 ` Kevin Ballard
2008-05-02 10:34 ` Wincent Colaiuta
2008-05-02 12:36 ` Jeff King [this message]
2008-05-02 13:49 ` Pedro Melo
2008-05-02 14:00 ` Aidan Van Dyk
2008-05-02 16:13 ` Wincent Colaiuta
2008-05-02 16:56 ` Kevin Ballard
2008-05-02 18:40 ` Wincent Colaiuta
2008-05-02 6:11 ` Jeff King
2008-05-02 7:53 ` Johannes Schindelin
2008-05-02 6:09 ` Jeff King
2008-05-02 6:19 ` Junio C Hamano
2008-05-02 12:55 ` Jeff King
2008-05-02 18:18 ` Junio C Hamano
2008-05-05 21:59 ` Jeff King
2008-05-06 5:51 ` Jeff King
2008-05-06 5:53 ` Jeff King
2008-05-11 17:15 ` Junio C Hamano
2008-05-16 4:42 ` Jeff King
2008-05-16 4:51 ` Jeff King
2008-05-16 10:29 ` Johannes Schindelin
2008-05-02 6:56 ` Jakub Narebski
2008-05-02 12:57 ` Jeff King
2008-05-02 15:36 ` Jeff King
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=20080502123656.GA2680@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@sb.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).