From: "Leo Razoumov" <slonik.az@gmail.com>
To: git@vger.kernel.org
Subject: Re: Fwd: git status options feature suggestion
Date: Sun, 12 Oct 2008 06:09:47 -0400 [thread overview]
Message-ID: <ee2a733e0810120309o1fbfa4dxe6f2292a28bd6db3@mail.gmail.com> (raw)
On 10/12/08, Junio C Hamano <gitster@pobox.com> wrote:
> [..snip..]
> 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.
>
Please, at least introduce a new option (--status-letters) that makes
git log --name-status
git diff --name-status
git ls-files -v
to use consistent letters to indicate the status. For details, see
recent discussion
http://www.spinics.net/lists/git/msg81141.html
Thanks,
--Leo--
next reply other threads:[~2008-10-12 10:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 10:09 Leo Razoumov [this message]
2008-10-18 0:19 ` Fwd: git status options feature suggestion Fyn Fynn
-- strict thread matches above, loose matches on Subject: below --
2008-10-09 5:34 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
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 8:26 ` Jeff King
2008-10-12 9:58 ` Junio C Hamano
2008-10-13 0:59 ` 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=ee2a733e0810120309o1fbfa4dxe6f2292a28bd6db3@mail.gmail.com \
--to=slonik.az@gmail.com \
--cc=git@vger.kernel.org \
/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).