"Michael P. Soulier" <msoulier@xxxxxxxxxxxxxxxx> wrote: > I'm finding this happening from time to time. > > soulierm@espresso:~/work/mitel-msl-tug$ git pull ... > error: Entry 'mitel-msl-tug.spec' not uptodate. Cannot merge. > soulierm@espresso:~/work/mitel-msl-tug$ git status > # On branch master > # Your branch is behind 'origin/master' by 4 commits, and can be fast-forwarded. > # > nothing to commit (working directory clean) ... > That directory is mounted via NFS, and I'm curious as to > whether some kind of time skew could be the problem. But > then, if it is, why did it go away after the first pull? Time or dev/ino skew in the index file vs. what we read from stat. Running git-status rematched the index file to the working directory, and during that rematch it noticed the file wasn't actually modified. So it prints "nothing to commit" and the next pull works fine, now that the stat data in the index matches the working directory. -- Shawn. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
