All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Tuncer Ayaz <tuncer.ayaz@gmail.com>,
	git@vger.kernel.org, gitster@pobox.com
Subject: Re: [RFC/PATCH] shortstatus v1
Date: Tue, 10 Feb 2009 13:36:56 +0100	[thread overview]
Message-ID: <499174E8.3030207@drmicha.warpmail.net> (raw)
In-Reply-To: <20090210114506.GF12089@coredump.intra.peff.net>

Jeff King venit, vidit, dixit 10.02.2009 12:45:
...
>> Right now, "git status" is basically "git commit --dry-run", which may
>> or may not be good, but certainly is not what people coming from other
>> vcs expect. I would suggest having "git commit -n" replace "git status"
>> if I hadn't done so already or if I dared to (I can't remember ;) ).
> 
> I would much prefer that, if it had been done that way from the
> beginning. But I think we are stuck with "git status" due to hysterical
> raisins.

ROTFTCOOTF!

Now I know why I never liked those caricatures of grapes...

>> "git ls-files" may do but has a different set of mode characters. I
>> think that sums up what preceeded Junio's patch from October.
> 
> But you only need to use it here to get the untracked files, so it
> doesn't matter what it says about modified files.
> 
> The big downside with the snippet I posted above is that it runs three
> separate commands that go through the index. In theory, you could do it
> in one pass. But wt-status _doesn't_ do that, since the diff
> infrastructure isn't there (a long time ago, Junio had an experimental
> parallel diff walker patch, but it never made it out of next).

We completely agree. How do you suggest to progress? Go for the diff
walker? For a (porc.) command like shortstatus I think going through the
index 3 times isn't that bad, all disk access should be cached after the
first run.

Michael

  reply	other threads:[~2009-02-10 12:38 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 [this message]
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
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=499174E8.3030207@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.