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

Re: [PATCH/RFC] gitk: refresh index before checking for local changes

From
Jon Seymour <jon.seymour@gmail.com>
Date
Apr 7, 2010, 14:36 UTC
Message-ID
<x2w2cfc40321004070736q7ab306b7i6220ffd58f724cec@mail.gmail.com>
In-Reply-To
<4BBBEC43.5000100@gmail.com>
On Wed, Apr 7, 2010 at 2:21 PM, A Large Angry SCM <gitzilla@gmail.com> wrote:
Show 5 quoted lines
>
> NAK - gitk should not modify a repository and/or working dir unless
> _explicitly_ prompted to by the user.
>
> If you want a new _non-default_ option setting for gitk, that fine also.
gitk and git gui currently behave differently in this regard.
git gui updates the indexes view of the working tree on start, gitk does not.
gitk's current behaviour is somewhat mysterious to the uninitiated -

user: "what? I have local changes?" tool: "relax dear user what you see is dirty laundry. if you want to see the actual state, start git gui then come back to me and refresh me when you are done"

gitk is effectively lying to the user about the state of their working tree. git gui does not.

Needless to say, I support this change.
jon.
Show 5 quoted lines
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Previous: Avery PennarunNext: Avery Pennarun
Message 13 of 15 in “gitk pays too much attention to file timestamps”
  1. Alexander GladyshApr 6, 2010
  2. Markus HeidelbergApr 6, 2010
  3. Jonathan NiederApr 6, 2010
  4. Alexander GladyshApr 6, 2010
  5. gitk: refresh index before checking for local changesJonathan Nieder, Apr 7, 2010
  6. Alexander GladyshApr 7, 2010
  7. Jonathan NiederApr 7, 2010
  8. A Large Angry SCMApr 7, 2010
  9. Jonathan NiederApr 7, 2010
  10. Junio C HamanoApr 7, 2010
  11. A Large Angry SCMApr 7, 2010
  12. Avery PennarunApr 7, 2010
  13. Jon SeymourApr 7, 2010
  14. Avery PennarunApr 6, 2010
  15. Jonathan NiederApr 7, 2010

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.