From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [BUG?] Working tree getting out of date "spontaneously"
Date: Fri, 5 Jun 2009 15:23:31 +0200 [thread overview]
Message-ID: <20090605132331.GC11035@atjola.homenet> (raw)
In-Reply-To: <200906051514.15876.robin.rosenberg.lists@dewire.com>
On 2009.06.05 15:14:15 +0200, Robin Rosenberg wrote:
> fredag 05 juni 2009 14:24:44 skrev Björn Steinbrink:
> > Hi,
> >
> > can't make any sense out of this at all:
> >
> > doener@atjola:git (master) $ git reset --hard HEAD@{1}
> > HEAD is now at b11cf09 Merge branch 'da/pretty-tempname'
> > doener@atjola:git (master) $ git update-ref refs/remotes/origin/master HEAD
> >
> > doener@atjola:git (master) $ git pull
> > From git://git.kernel.org/pub/scm/git/git
> > b11cf09..6096d75 master -> origin/master
> > Updating b11cf09..6096d75
> > Fast forward
> > Documentation/RelNotes-1.6.3.2.txt | 12 +++++-------
> > Documentation/git.txt | 7 ++++++-
> > contrib/completion/git-completion.bash | 12 ++++++++++--
> > grep.c | 6 +++++-
> > 4 files changed, 26 insertions(+), 11 deletions(-)
> >
> > doener@atjola:git (master) $ git diff-index --name-only HEAD
> > doener@atjola:git (master) $ git diff-index --name-only --cached HEAD
> >
> > *wait a minute, doing nothing*
> >
> > doener@atjola:git (master) $ git diff-index --name-only HEAD
> > Documentation/RelNotes-1.6.3.2.txt
> > Documentation/git.txt
> > contrib/completion/git-completion.bash
> > grep.c
> >
> > doener@atjola:git (master) $ git diff-index --name-only --cached HEAD
> >
> > doener@atjola:git (master) $ git diff-index --stat HEAD
> > 0 files changed, 0 insertions(+), 0 deletions(-)
> >
> > doener@atjola:git (master) $ git diff-index --name-only HEAD
> > Documentation/RelNotes-1.6.3.2.txt
> > Documentation/git.txt
> > contrib/completion/git-completion.bash
> > grep.c
> >
> >
> > Running "git status" seems to fix things.
> >
> > Björn, confused
>
> What file system and OS?
Linux 2.6.30-rc8, ext4. ctime gets updated for no apparent reason, see
the other mail I just sent.
Thanks,
Björn
next prev parent reply other threads:[~2009-06-05 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 12:24 [BUG?] Working tree getting out of date "spontaneously" Björn Steinbrink
2009-06-05 13:14 ` Robin Rosenberg
2009-06-05 13:23 ` Björn Steinbrink [this message]
2009-06-05 13:21 ` [BUG ext4?] " Björn Steinbrink
2009-06-05 14:12 ` Björn Steinbrink
2009-06-05 14:47 ` [BUG? ext4] git working " Björn Steinbrink
2009-06-05 14:55 ` [BUG ext4?] Working " Theodore Tso
2009-06-05 15:02 ` Björn Steinbrink
2009-06-05 18:06 ` Theodore Tso
2009-06-05 18:35 ` Björn Steinbrink
2009-06-05 21:38 ` Theodore Tso
2009-06-05 15:39 ` Linus Torvalds
2009-06-05 16:14 ` Björn Steinbrink
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090605132331.GC11035@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).