From: "Carlos Martín Nieto" <cmn@elego.de>
To: Chris Patti <cpatti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Odd issue - The Diffs That WILL NOT DIE.
Date: Tue, 6 Dec 2011 22:51:03 +0100 [thread overview]
Message-ID: <20111206215102.GA3654@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <CAJ8P3RBm=RhNf6LKLqprqX6Rqx0OgRnJR+=+-Qhg4PvpeqaUDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Tue, Dec 06, 2011 at 04:43:50PM -0500, Chris Patti wrote:
> I have a Homebrew installed version if Git 1.7.8 running on OSX Lion.
>
> I'm seeing a very odd issue where these diffs I didn't create keep
> recurring in a particular repository.
Which diffs? You haven't given us any? What files does this happen
with? Do they have any peculiarities?
If these are files with non-ASCII filenames, then you're hitting a
misfeature of the HFS+ filesystem (it lies when git asks it about
files).
>
> I've tried:
>
> * Nuking the repo and re-cloning, cloning into a totally different
> containing directory
> * git reset --hard, git checkout -- of the offending file supposedly
> containing the diffs
>
> Is there some sort of uber persistent local cache that's bound to the
> remote repository?
The remote repository shouldn't have anything to do with this.
cmn
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-12-06 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 21:43 Odd issue - The Diffs That WILL NOT DIE Chris Patti
2011-12-06 21:47 ` Frans Klaver
2011-12-06 21:51 ` Carlos Martín Nieto [this message]
2011-12-07 16:54 ` Chris Patti
2011-12-07 17:20 ` Philippe Vaucher
2011-12-07 18:05 ` Chris Patti
2011-12-07 18:16 ` Chris Patti
2011-12-07 22:03 ` Jeff King
2011-12-07 22:24 ` Chris Patti
2011-12-07 22:30 ` Chris Patti
2011-12-07 22:58 ` Carlos Martín Nieto
2011-12-07 23:06 ` Jeff King
2012-09-05 19:38 ` Robin Rosenberg
2011-12-07 23:03 ` Jeff King
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=20111206215102.GA3654@centaur.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=cpatti@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).