public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web•de>
To: Alexander Gladysh <agladysh@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: gitk pays too much attention to file timestamps
Date: Wed, 7 Apr 2010 01:15:27 +0200	[thread overview]
Message-ID: <201004070115.27285.markus.heidelberg@web.de> (raw)
In-Reply-To: <l2hc6c947f61004061557x8085600fif5e973077d9eb4f3@mail.gmail.com>

Alexander Gladysh, 2010-04-07 00:57:
> Hi, list!
> 
> OS X 10.6.3
> Git 1.7.0.4
> 
> When I "touch" a file, gitk lists it in "local uncommitted changes,
> not checked in to index" (without a difference, just a name). I
> believe that it should not.
> 
> Git status, and git commit do ignore such files.
> 
> After git reset --hard, gitk stops seeing changes as expected.

The problem is that gitk doesn't invoke "git update-index --refresh",
I guess it should on Update (F5) and Reload (Ctrl-F5).

Markus

  reply	other threads:[~2010-04-06 23:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:57 gitk pays too much attention to file timestamps Alexander Gladysh
2010-04-06 23:15 ` Markus Heidelberg [this message]
2010-04-06 23:36 ` Jonathan Nieder
2010-04-06 23:47   ` Alexander Gladysh
2010-04-07  0:43     ` [PATCH/RFC] gitk: refresh index before checking for local changes Jonathan Nieder
2010-04-07  1:07       ` Alexander Gladysh
2010-04-07  1:16       ` Jonathan Nieder
2010-04-07  2:21       ` A Large Angry SCM
2010-04-07  2:57         ` Jonathan Nieder
2010-04-07  5:47         ` Junio C Hamano
2010-04-07 11:21           ` A Large Angry SCM
2010-04-07 16:48           ` Avery Pennarun
2010-04-07 14:36         ` Jon Seymour
2010-04-06 23:58   ` gitk pays too much attention to file timestamps Avery Pennarun
2010-04-07  1:01     ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004070115.27285.markus.heidelberg@web.de \
    --to=markus.heidelberg@web$(echo .)de \
    --cc=agladysh@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox