From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: how to revert changes in working tree?
Date: Wed, 06 Dec 2006 11:20:51 +0100 [thread overview]
Message-ID: <el65e6$tfj$1@sea.gmane.org> (raw)
In-Reply-To: 45769417.70601@gmail.com
Liu Yubao wrote:
>> Do a "git repo-config core.filemode false" to almost
>> disable the checks for exec bit.
>>
>
> It has been set. I guess the cause is a interrupted merge
> operation that leads to textual difference.
Try also "git repo-config core.ignoreStat true". Perhaps it would help.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-12-06 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 6:49 how to revert changes in working tree? Liu Yubao
2006-12-06 8:43 ` Alex Riesen
2006-12-06 9:57 ` Liu Yubao
2006-12-06 10:20 ` Alex Riesen
2006-12-06 11:14 ` Liu Yubao
2006-12-06 12:30 ` Alex Riesen
2006-12-06 12:52 ` Jakub Narebski
2006-12-06 18:13 ` Shawn Pearce
2006-12-07 1:42 ` Liu Yubao
2006-12-07 7:15 ` Juergen Ruehle
2006-12-06 10:20 ` Jakub Narebski [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='el65e6$tfj$1@sea.gmane.org' \
--to=jnareb@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).