From: "J. Bruce Fields" <bfields@fieldses.org>
To: git@vger.kernel.org
Subject: odd behavior with concurrent fetch/checkout
Date: Mon, 22 Oct 2007 12:51:25 -0400 [thread overview]
Message-ID: <20071022165125.GG583@fieldses.org> (raw)
Just now I checked out a topic branch in my working repo:
git checkout server-xprt-switch
and while waiting for it to complete (I just started work and caches
were all cold), I ran a
git fetch origin
in another window to update from Linus. The git fetch gave a warning:
remote: Generating pack...
remote: Counting objects: 7550
remote: Done counting 12885 objects.
remote: Result has 8400 objects.
remote: Deltifying 8400 objects...
remote: 100% (8400/8400) done
Indexing 8400 objects...
remote: Total 8400 (delta 7257), reused 5696 (delta 4586)
100% (8400/8400) done
Resolving 7257 deltas...
100% (7257/7257) done
* refs/remotes/origin/master: fast forward to branch 'master' of
* git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
old..new: d85714d..55b70a0
Cannot fetch into the current branch.
Why the warning? Also, afterwards I was left with server-xprt-switch
pointing to the tip of the branch I'd just switched from (another
miscellaneous topic branch). The working directory was in some
completely different state--thanks to a quick reset --hard I don't know
what it was. Also, in the reflog for the checked-out branch:
commit bac1e7977eb4781e62cee7f1c7c3d13a9e5d8d74
Reflog: server-xprt-switch@{0} (J. Bruce Fields <bfields@citi.umich.edu>)
Reflog message: fetch origin: Undoing incorrectly fetched HEAD.
Author: J. Bruce Fields <bfields@citi.umich.edu>
Date: Mon Oct 22 12:32:37 2007 -0400
...
Why was a fetch into the remote fooling with HEAD or anything under
refs/heads/?
--b.
next reply other threads:[~2007-10-22 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 16:51 J. Bruce Fields [this message]
2007-10-22 19:46 ` odd behavior with concurrent fetch/checkout J. Bruce Fields
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=20071022165125.GG583@fieldses.org \
--to=bfields@fieldses.org \
--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).