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
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 7, 2010, 16:48 UTC
Message-ID
<r2l32541b131004070948o92575f5j4728764482e8a262@mail.gmail.com>
In-Reply-To
<7vfx37g6f6.fsf@alter.siamese.dyndns.org>
On Wed, Apr 7, 2010 at 1:47 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
> A Large Angry SCM <gitzilla@gmail.com> writes:
>> NAK - gitk should not modify a repository and/or working dir unless
>> _explicitly_ prompted to by the user.
>
> I used to think that way, until I realized that gitk has operations like
> "Tag this commit" that does write into the repository.

Also 'git status' does the same "modify a repository" operation as we're currently discussing, so calling it modification is a bit of an exaggeration.

Avery
Previous: A Large Angry SCMNext: Jon Seymour
Message 12 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.