From: Thomas Rast <trast@student.ethz.ch>
To: Oliver Kullmann <O.Kullmann@swansea.ac.uk>
Cc: git@vger.kernel.org
Subject: Re: strange temporary pull-errors
Date: Sat, 23 Aug 2008 10:44:45 +0200 [thread overview]
Message-ID: <200808231044.50797.trast@student.ethz.ch> (raw)
In-Reply-To: <20080822191324.GO10819@cs-wsok.swansea.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Oliver Kullmann wrote:
>
> > git pull
[...]
> error: Entry 'Buildsystem/Configuration/Html/local_html.mak' not uptodate. Cannot merge.
[...]
> > git status
[...]
> nothing to commit (working directory clean)
> > git pull
[succeeds]
> There is nothing special going out, the simple pull should succeed, but
> I have to try several times; don't know whether the "git status" is
> instrumental here or not --- will try the next time.
Saying 'git status' refreshes the index. If you have touched (updated
mtime) local_html.mak without making any changes, 'git merge' just
compared the mtime and considered the file changed. But 'git status'
actually compares the contents and finds it has not been changed. I
don't know whether 1.6 (most likely builtin-merge) changed behaviour
in this respect, maybe you could try with an older version too.
There are other cases where you need a refresh, for example if you
have made a copy of a git-tracked directory with 'cp -r'.
- Thomas
--
Thomas Rast
trast@student.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-23 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 19:13 strange temporary pull-errors Oliver Kullmann
2008-08-23 8:44 ` Thomas Rast [this message]
2008-08-23 17:35 ` Miklos Vajna
-- strict thread matches above, loose matches on Subject: below --
2008-08-25 18:38 Oliver Kullmann
2008-08-25 19:39 ` Miklos Vajna
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=200808231044.50797.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=O.Kullmann@swansea.ac.uk \
--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).