From: Avery Pennarun <apenwarr@gmail.com>
To: Jody McIntyre <scjody@sun.com>
Cc: git@vger.kernel.org
Subject: Re: 'git pull' fails with 'not uptodate' message despite 'git reset --hard'
Date: Tue, 28 Jul 2009 20:19:54 -0400 [thread overview]
Message-ID: <32541b130907281719y57862c25w524f5bbf1df11c40@mail.gmail.com> (raw)
In-Reply-To: <20090728230842.GE22281@clouds>
On Tue, Jul 28, 2009 at 7:08 PM, Jody McIntyre<scjody@sun.com> wrote:
> I am attempting to update my kernel tree but getting a 'not uptodate' error:
>
> $ git fetch origin
> [...]
> $ git pull origin tags/v2.6.31-rc4
> From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
> * tag v2.6.31-rc4 -> FETCH_HEAD
> Updating 6847e15..4be3bd7
> error: Entry 'CREDITS' not uptodate. Cannot merge.
[...]
> I use quilt with this tree but no quilt patches are currently applied and it
> should be clean. It hasn't even been built (I rsync to another machine for
> that.)
I've run into this problem when I rsync a tree from one system to
another. The inodes will be different, so merge will think files in
the work tree have changed, but then diff (of course) won't see
anything because it looks at the actual file contents, which are
identical.
Usually a 'git status' will fix it. In any case, if it doesn't,
please send the output of 'git status' :)
I believe this cache out-of-dateness issue was fixed in a recent version of git.
Have fun,
Avery
next prev parent reply other threads:[~2009-07-29 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 23:08 'git pull' fails with 'not uptodate' message despite 'git reset --hard' Jody McIntyre
2009-07-29 0:19 ` Avery Pennarun [this message]
2009-07-29 20:36 ` Jody McIntyre
2009-07-29 20:44 ` Avery Pennarun
2009-07-29 22:54 ` Jody McIntyre
2009-07-30 15:40 ` Jody McIntyre
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=32541b130907281719y57862c25w524f5bbf1df11c40@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=scjody@sun.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.
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).