From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Caleb Cushing <xenoterracide@gmail.com>,
git@vger.kernel.org
Subject: Re: Fwd: git status options feature suggestion
Date: Sat, 11 Oct 2008 23:41:18 -0700 [thread overview]
Message-ID: <7vwsgegvsh.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081012044900.GA27845@coredump.intra.peff.net> (Jeff King's message of "Sun, 12 Oct 2008 00:49:00 -0400")
Jeff King <peff@peff.net> writes:
> So I think it is probably reasonable to think about a new command (which
> would not be called status) that shows this information.
I was going to suggest the same. "git st" for people who come from "svn st"
so that "git status" can be kept as traditional "preview of 'git commit'".
And just make it mimic whatever folks accustomed to "svn st" would expect,
modulo we would need two status letters to signal difference between
(HEAD, index), and (index, worktree). Perhaps three if you want to show
difference between (HEAD, worktree) while at it.
And no, I have not seen any argument good enough to change ls-files nor
diff-$lowlevel output and break people's existing scripts.
next prev parent reply other threads:[~2008-10-12 6:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 5:34 git status options feature suggestion Caleb Cushing
2008-10-09 6:11 ` Jeff King
[not found] ` <81bfc67a0810082327p421ca4e9v84f4b33023bc6fe6@mail.gmail.com>
2008-10-09 6:27 ` Fwd: " Caleb Cushing
2008-10-09 9:03 ` Johannes Schindelin
2008-10-09 15:12 ` Michael J Gruber
2008-10-10 2:20 ` Caleb Cushing
2008-10-10 4:25 ` Elijah Newren
2008-10-10 11:13 ` Johannes Schindelin
2008-10-12 4:49 ` Jeff King
2008-10-12 6:41 ` Junio C Hamano [this message]
2008-10-12 6:45 ` Jeff King
2008-10-12 8:10 ` Junio C Hamano
2008-10-13 1:04 ` Jeff King
2008-10-13 1:30 ` Shawn O. Pearce
2008-10-26 1:47 ` Junio C Hamano
2008-10-26 4:59 ` Jeff King
2008-10-12 18:05 ` Shawn O. Pearce
2008-10-13 1:06 ` Jeff King
2008-10-12 9:07 ` Jakub Narebski
2008-10-12 10:47 ` Wincent Colaiuta
2008-10-12 11:40 ` Teemu Likonen
2008-10-12 13:52 ` Andreas Ericsson
2008-10-12 8:26 ` Fwd: " Jeff King
2008-10-12 9:58 ` Junio C Hamano
2008-10-13 0:59 ` Jeff King
2008-10-09 21:23 ` ls-files [Was: Re: Fwd: git status options feature suggestion] James Cloos
2008-10-09 21:41 ` Shawn O. Pearce
2008-10-09 22:13 ` Jeremy Ramer
2008-10-09 22:52 ` ls-files James Cloos
-- strict thread matches above, loose matches on Subject: below --
2008-10-12 10:09 Fwd: git status options feature suggestion Leo Razoumov
2008-10-18 0:19 ` Fyn Fynn
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=7vwsgegvsh.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=xenoterracide@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).