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

Re: [PATCH] bash: offer to show (un)staged changes

From
TATuncer Ayaz <tuncer.ayaz@gmail.com>
Date
Feb 2, 2009, 00:50 UTC
Message-ID
<4ac8254d0902011650g714c5a7cya3c5111a74b8d8ea@mail.gmail.com>
In-Reply-To
<7vwsc9rae9.fsf@gitster.siamese.dyndns.org>
On Mon, Feb 2, 2009 at 12:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 29 quoted lines
> Tuncer Ayaz <tuncer.ayaz@gmail.com> writes:
>
>> On Mon, Jan 19, 2009 at 6:29 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
>>> Junio C Hamano <gitster@pobox.com> wrote:
>>>> Thomas Rast <trast@student.ethz.ch> writes:
>>>>
>>>> > +           if test ! -z "$GIT_PS1_EXPENSIVE"; then
>>>> > +                   git update-index --refresh >/dev/null 2>&1 || w="*"
>>>>
>>>> This makes the feature unavailable for people who care about the stat
>>>> dirtiness and explicitly set diff.autorefreshindex to false, doesn't it?
>>>
>>> Yup, and I'm one of those people who sets autorefresindex to false
>>> in my ~/.gitconfig, usually before I even have user.{name,email} set.
>>>
>>> I do like the idea of what Thomas is trying to do here, but its
>>> so bloody expensive to compute dirty state on every prompt in
>>> some repositories that I'd shoot myself.  E.g. WebKit is huge,
>>
>> I've been thinking about this and wondered
>> whether implementing "status --mini" or
>> "status --short" which prints "+?*" in wt-status.c
>> could be made fast enough.
>>
>> Should we try to implement and profile this
>> or do we know it will be slow beforehand?
>
> I think I've seen a patch to do something like that, soon after Shawn
> announced his repo tool.
The best I could find is your patch from October 25th 2008
which implements:
       $ ./git-shortstatus
       M     Makefile
       R100  COPYING -> RENAMING
           M builtin-commit.c
           M builtin-revert.c
           M builtin.h
           M git.c
           M wt-status.c
           M wt-status.h
Is this what you meant?
Previous: Junio C HamanoNext: Tuncer Ayaz
Message 19 of 22 in “bash: offer to show (un)staged changes”
  1. bash: offer to show (un)staged changesThomas Rast, Jan 18, 2009
  2. Junio C HamanoJan 18, 2009
  3. Thomas RastJan 18, 2009
  4. Shawn O. PearceJan 19, 2009
  5. Martin LanghoffJan 19, 2009
  6. Shawn O. PearceJan 19, 2009
  7. Mike HommeyJan 19, 2009
  8. Martin LanghoffJan 19, 2009
  9. Boyd Stephen Smith Jr.Jan 19, 2009
  10. Martin LanghoffJan 19, 2009
  11. Boyd Stephen Smith Jr.Jan 19, 2009
  12. bash: offer to show (un)staged changesThomas Rast, Jan 19, 2009
  13. bash: offer to show (un)staged changesThomas Rast, Feb 1, 2009
  14. Shawn O. PearceFeb 1, 2009
  15. bash: offer to show (un)staged changesThomas Rast, Feb 3, 2009
  16. Shawn O. PearceFeb 3, 2009
  17. Tuncer AyazFeb 1, 2009
  18. Junio C HamanoFeb 1, 2009
  19. Tuncer AyazFeb 2, 2009
  20. Tuncer AyazFeb 2, 2009
  21. Junio C HamanoJan 18, 2009
  22. Thomas RastJan 18, 2009

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.