From: Junio C Hamano <hidden> Date: 2016-06-15 22:45:28
Jeff King [off-list ref] 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.
From: Jeff King <hidden> Date: 2016-06-15 22:45:28
On Sat, Oct 11, 2008 at 11:41:18PM -0700, Junio C Hamano wrote:
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.
I remember a long time ago you started on a parallel diff walker that
could diff the working tree, the index, and a tree at once. Do you
remember the issues with it?
I think that would be the right tool here to show each file only once,
but with multiple status flags. Something like:
A M foo
to show that "foo" has been added since the last commit, but there are
modifications in the working tree that have not yet been staged.
-Peff
El 12/10/2008, a las 8:41, Junio C Hamano escribió:
Jeff King [off-list ref] writes:
quoted
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.
One of the first aliases I set up when I started using git was "st" for status, and I'd imagine that's a pretty common thing for people coming from other SCMs like svn and cvs. But I very quickly became used to git's notion of what "status" means and I wouldn't want "git st" to start giving me a different behaviour.
I think if you're introducing a different command then you should make sure it doesn't happen to be an abbreviation of an existing one. It would be better to give it some other name (info, foo, whatever). If svn people then want to make an "st" alias pointing to it they're free to do so.
Just my 2c.
Cheers,
Wincent
From: Shawn O. Pearce <hidden> Date: 2016-06-15 22:45:28
Jeff King [off-list ref] wrote:
On Sat, Oct 11, 2008 at 11:41:18PM -0700, Junio C Hamano wrote:
quoted
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.
I remember a long time ago you started on a parallel diff walker that
could diff the working tree, the index, and a tree at once. Do you
remember the issues with it?
I think that would be the right tool here to show each file only once,
but with multiple status flags. Something like:
A M foo
I have a tool that I'll be open-sourcing later this year, but it does
something like that:
project foo/ branch master
Am foo
M- bar
R- orig => dest ( 95%)
Line coloring is red on lines with unstaged stuff in the working
directory (3rd column, lower case letters) and green on lines that
are fully staged (3rd column is a '-').
The tool is in Python, but I'm just scraping the output of
`diff-index -M --cached HEAD` and diff-files to get that
display. The status letters are exactly those given out by
diff-index/diff-files, but the diff-files output is lowercased.
Scott Chacon has seen the tool output and likes it; there's a tech
talk that will be posted on YouTube soon where he and I are sort
of talking about it.
Sorry I can't say too much more about it yet. But I'm trying to
say that both Scott and I like a denser display like this.
--
Shawn.
From: Jeff King <hidden> Date: 2016-06-15 22:45:28
On Sun, Oct 12, 2008 at 11:05:04AM -0700, Shawn O. Pearce wrote:
I have a tool that I'll be open-sourcing later this year, but it does
[...]
Sorry I can't say too much more about it yet. But I'm trying to
say that both Scott and I like a denser display like this.
I like what I saw, and I think a "denser" format is what I was trying to
suggest in my earlier message (I just didn't think of nearly as clear a
word). So count me in for your list of people who would like to see this
thing (and would even work on doing a pure-C version).
-Peff