git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Gladysh <agladysh@gmail.com>
To: git@vger.kernel.org
Subject: gitk pays too much attention to file timestamps
Date: Wed, 7 Apr 2010 02:57:00 +0400	[thread overview]
Message-ID: <l2hc6c947f61004061557x8085600fif5e973077d9eb4f3@mail.gmail.com> (raw)

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.

See steps to reproduce below.

HTH,
Alexander.

$ mkdir touch
$ cd touch
$ git init
$ echo "A" > alpha
$ git add alpha
$ git commit -m "alpha"
$ touch alpha
$ git status
# On branch master
nothing to commit (working directory clean)
$ gitk --all

Observe "local uncommitted changes, not checked in to index"

             reply	other threads:[~2010-04-06 22:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:57 Alexander Gladysh [this message]
2010-04-06 23:15 ` gitk pays too much attention to file timestamps Markus Heidelberg
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=l2hc6c947f61004061557x8085600fif5e973077d9eb4f3@mail.gmail.com \
    --to=agladysh@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).