From: Chris Packham <judge.packham@gmail.com>
To: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: change in behaviour of git status and/or gitk bug
Date: Fri, 7 May 2010 09:47:16 -0700 [thread overview]
Message-ID: <i2qa038bef51005070947w489883f2n510bb824e667fd5@mail.gmail.com> (raw)
In-Reply-To: <20100507050054.GA25987@coredump.intra.peff.net>
On Thu, May 6, 2010 at 10:00 PM, Jeff King <peff@peff.net> wrote:
> On Thu, May 06, 2010 at 06:20:34PM -0700, Chris Packham wrote:
>
>> I noticed a while back that with gitk I kept on getting files shown as
>> "Local uncommitted changes, not checked in to index" when I'd made
>> modifications to them then backed them out so the working tree content
>> was the same as the index. I used to (with git 1.6.x) fix / work
>> around this by running git status.
>>
>> Now, with git 1.7.1, that workaround has stopped working. No doubt
>
> This was lost in v1.7.0, but should be back in v1.7.2. The actual fix is
> 4bb6644 (git status: refresh the index if possible, 2010-04-02).
>
> You can run "git update-index --refresh" to get the same effect. Running
> "git diff" also works.
>
> There was some talk (and a patch) recently about gitk running
> "update-index --refresh", but I don't know if it got picked up. See:
>
> http://article.gmane.org/gmane.comp.version-control.git/144182
>
> -Peff
>
OK good to know its not just me.
I'd add my vote for gitk running "update-index --refresh" in response
to a user asking it to refresh, which should satisfy the "gitk doesn't
touch anything unless you ask it to" requirement.
prev parent reply other threads:[~2010-05-07 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 1:20 change in behaviour of git status and/or gitk bug Chris Packham
2010-05-07 5:00 ` Jeff King
2010-05-07 16:47 ` Chris Packham [this message]
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=i2qa038bef51005070947w489883f2n510bb824e667fd5@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).