From: Mike Hommey <mh@glandium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Strange "beagle" interaction..
Date: Tue, 13 Nov 2007 22:55:28 +0100 [thread overview]
Message-ID: <20071113215528.GA30695@glandium.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711131241050.2786@woody.linux-foundation.org>
On Tue, Nov 13, 2007 at 12:56:19PM -0800, Linus Torvalds wrote:
>
> Ok, I've made a bugzilla entry for this for the Fedora people, but I
> thought I'd mention something I noticed yesterday but only tracked down
> today: it seems like the beagle file indexing code is able to screw up git
> in subtle ways.
>
> I do not know exactly what happens, but the symptoms are random (and
> quite hard-to-trigger) dirty index contents where git believes that some
> set of files are not clean in the index.
>
> I *suspect* that beagle is playing games with the file access times,
> causing the ctime on disk to not match the ce_ctime in the index file. But
> that's just a guess.
(...)
IIRC, beagle stores a bunch of useful information for itself in extended
attributes on indexed files. It is likely that it's that that is
tampering with the file stats.
Mike
prev parent reply other threads:[~2007-11-13 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 20:56 Strange "beagle" interaction Linus Torvalds
2007-11-13 21:03 ` J. Bruce Fields
2007-11-13 21:21 ` J. Bruce Fields
2007-11-13 21:30 ` Linus Torvalds
2007-11-13 21:44 ` Jon Smirl
2007-11-13 21:49 ` David Brown
2007-11-13 21:50 ` J. Bruce Fields
2007-11-13 21:58 ` Jon Smirl
2007-11-13 21:55 ` Mike Hommey [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=20071113215528.GA30695@glandium.org \
--to=mh@glandium.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.