From: Junio C Hamano <gitster@pobox.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: git-checkout sometimes silently fails
Date: Tue, 06 May 2008 17:19:01 -0700 [thread overview]
Message-ID: <7v4p9bge4q.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080506171052.340d643e.akpm@linux-foundation.org> (Andrew Morton's message of "Tue, 6 May 2008 17:10:52 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> y:/usr/src/git26> git-branch -av | grep '^\*'
> * master 5717922 Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb
> y:/usr/src/git26> git-checkout linux-next
> Switched to branch "linux-next"
> y:/usr/src/git26> git-branch -av | grep '^\*'
> * linux-next 5717922 Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb
So your two local branches 'master' and 'linux-next' both point at the
same commit, 5717922.
"git checkout <branchname>" is to check out the local branch name. You
expect "git checkout master" and then "git checkout linux-next" to check
out two different commits because linux-next _should_ have been updated to
the latest from sfr repository. But it appears to me that that is not the
case.
Perhaps "git fetch linux-next" hasn't been run, before "git checkout" was
attempted?
next prev parent reply other threads:[~2008-05-07 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 19:22 git-checkout sometimes silently fails Andrew Morton
2008-05-06 21:50 ` Alex Riesen
2008-05-07 0:10 ` Andrew Morton
2008-05-07 0:19 ` Junio C Hamano [this message]
2008-05-07 0:43 ` Andrew Morton
2008-05-07 15:09 ` J. Bruce Fields
2008-05-07 0:19 ` Jeff King
2008-05-07 0:54 ` Andrew Morton
2008-05-07 1:32 ` Björn Steinbrink
2008-05-07 8:51 ` Johannes Sixt
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=7v4p9bge4q.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.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).