From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tuncer Ayaz <tuncer.ayaz@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] shortstatus v1
Date: Tue, 10 Feb 2009 13:22:14 -0500 [thread overview]
Message-ID: <20090210182214.GA19957@coredump.intra.peff.net> (raw)
In-Reply-To: <20090210181052.GA19634@coredump.intra.peff.net>
On Tue, Feb 10, 2009 at 01:10:52PM -0500, Jeff King wrote:
> - I don't think the "mini" status is really related to this. The novel
> thing here is collating the outputs into a single sorted list. But
> the "mini" output is not about that at all:
>
> 1. It doesn't care about full output, so it should be able to exit
> early from the diff, avoid rename detection, etc, so that it is
> as quick as possible.
>
> 2. It doesn't collate the output at all. It is about three
> separate symbols for the three separate lists.
Oh, sorry, I was misreading the "mini" output. I thought the three flags
corresponded to the staged, unstaged, and untracked changes. But they
are "unstaged or staged but added", "unstaged or staged but changed", or
"untracked" (although right now the last is triggered by unmerged
entries?).
I honestly don't see much point in differentiating added versus changed
files. Splitting it into "some things are staged" and "some things are
not staged" makes more sense to me. But if you do want that distinction
then an early exit from the diff is more complicated (since you might
have to keep going to see if there are any of _either_ type).
-Peff
next prev parent reply other threads:[~2009-02-10 18:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 0:51 [RFC/PATCH] shortstatus v1 Tuncer Ayaz
2009-02-10 1:44 ` Junio C Hamano
2009-02-10 3:46 ` Sitaram Chamarty
2009-02-10 10:22 ` Spending time in PS1, was " Johannes Schindelin
2009-02-10 17:31 ` Sitaram Chamarty
2009-02-10 10:11 ` Tuncer Ayaz
2009-02-10 11:03 ` Jeff King
2009-02-10 11:29 ` Michael J Gruber
2009-02-10 11:31 ` Tuncer Ayaz
2009-02-10 11:45 ` Jeff King
2009-02-10 12:36 ` Michael J Gruber
2009-02-10 13:01 ` Jeff King
2009-02-10 15:58 ` Junio C Hamano
2009-02-10 18:10 ` Jeff King
2009-02-10 18:22 ` Jeff King [this message]
2009-02-10 19:11 ` Jeff King
2009-02-10 21:21 ` Tuncer Ayaz
2009-02-10 21:36 ` Jeff King
2009-02-10 22:25 ` Junio C Hamano
2009-02-10 22:52 ` Tuncer Ayaz
2009-02-10 22:55 ` Jeff King
2009-02-10 23:05 ` Junio C Hamano
2009-02-12 0:49 ` Jeff King
2009-02-10 23:52 ` Nanako Shiraishi
2009-02-11 21:24 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 23:58 [RFC] New command: 'git snapshot' Ulrik Sverdrup
2009-02-11 0:08 ` [RFC/PATCH] shortstatus v1 Nanako Shiraishi
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=20090210182214.GA19957@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tuncer.ayaz@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;
as well as URLs for NNTP newsgroup(s).