git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git status options feature suggestion

From
Wincent Colaiuta <win@wincent.com>
Date
Oct 12, 2008, 10:47 UTC
Message-ID
<971DCAD3-3274-4507-AE3D-5BDCEDB8513C@wincent.com>
In-Reply-To
<7vwsgegvsh.fsf@gitster.siamese.dyndns.org>
El 12/10/2008, a las 8:41, Junio C Hamano escribió:
Show 17 quoted lines
> 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.

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

Previous: Jakub NarebskiNext: Teemu Likonen
Message 20 of 29 in “git status options feature suggestion”
  1. Caleb CushingOct 9, 2008
  2. Jeff KingOct 9, 2008
  3. Fwd: git status options feature suggestionCaleb Cushing, Oct 9, 2008
  4. Johannes SchindelinOct 9, 2008
  5. Michael J GruberOct 9, 2008
  6. Caleb CushingOct 10, 2008
  7. Elijah NewrenOct 10, 2008
  8. Johannes SchindelinOct 10, 2008
  9. Jeff KingOct 12, 2008
  10. Junio C HamanoOct 12, 2008
  11. Jeff KingOct 12, 2008
  12. Junio C HamanoOct 12, 2008
  13. Jeff KingOct 13, 2008
  14. Shawn O. PearceOct 13, 2008
  15. Junio C HamanoOct 26, 2008
  16. Jeff KingOct 26, 2008
  17. Shawn O. PearceOct 12, 2008
  18. Jeff KingOct 13, 2008
  19. Jakub NarebskiOct 12, 2008
  20. Wincent ColaiutaOct 12, 2008
  21. Teemu LikonenOct 12, 2008
  22. Andreas EricssonOct 12, 2008
  23. Jeff KingOct 12, 2008
  24. Junio C HamanoOct 12, 2008
  25. Jeff KingOct 13, 2008
  26. ls-files [Was: Re: Fwd: git status options feature suggestion]James Cloos, Oct 9, 2008
  27. Shawn O. PearceOct 9, 2008
  28. Jeremy RamerOct 9, 2008
  29. James CloosOct 9, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.