On Sun, Jun 22, 2008 at 02:48:35PM +0200, Mikael Magnusson wrote: > 2008/6/22 Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx>: > > Hello, Ingo, > > > > I took the precaution of rebuilding my linux-2.6-tip from scratch as follows: > > > > 544 mkdir linux-2.6-tip > > 545 cd linux-2.6-tip > > 546 git-init-db > > 547 git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > 548 git-remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git > > 549 git-remote update > > 550 git-checkout tip-core-rcu-2008-06-16_09.23_Mon > > When checking out remote branches, you have to specify the remote: > git checkout tip/tip-blabla > (it'll warn about detaching HEAD, this is normal). Thank you, Mikael! But when I try "git-checkout tip/tip-core-rcu-2008-06-16_09.23_Mon", it says: error: pathspec 'tip/tip-core-rcu-2008-06-16_09.23_Mon' did not match any file(s) known to git. Did you forget to 'git add'? Trying "git-checkout tip/tip-core-rcu" gets me: error: pathspec 'tip/tip-core-rcu' did not match any file(s) known to git. Did you forget to 'git add'? Trying "git-checkout -b tip-core-rcu tip/tip-core-rcu" gets me: git checkout: updating paths is incompatible with switching branches/forcing Did you intend to checkout 'tip/tip-core-rcu' which can not be resolved as commit? Trying "git-checkout -b tip-core-rcu tip/tip-core-rcu-2008-06-16_09.23_Mon" gets me: git checkout: updating paths is incompatible with switching branches/forcing Did you intend to checkout 'tip/tip-core-rcu-2008-06-16_09.23_Mon' which can not be resolved as commit? Trying "git-checkout -b tip-core-rcu tip-core-rcu-2008-06-16_09.23_Mon" acts like it is doing something useful, but doesn't find the recent updates, which I believe happened -before- June 16 2008. Help??? Thanx, Paul -- 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
