On Sat, 2012-01-28 at 17:51 +0000, Stefan Kuhne wrote:> Hello,
>
> I''ll compile a 2.6.32 kernel from xen git.
> I follow: http://wiki.xen.org/wiki/Compiling_Kernel_2.6.32
>
> But i get:
>
> git checkout: updating paths is incompatible with switching
branches/forcing
> Did you intend to checkout ''origin/xen/stable-2.6.32.x''
which can not be
> resolved as commit?
>
> Any ideas?
Is there some reason you want to use 2.6.32 in particular? Although it
is still a longterm maintained kernel upstream I think this is due to
end fairly shortly. If possible you should switch to one of the more
recent upstream kernels e.g. v3.2. You can get these direct from
kernel.org.
If you really think you need 2.6.32.x then you can either:
Use the xen/next-2.6.32 branch of that tree instead. This is the
pre-testing branch which would become xen/stable-2.6.32.x after
automated testing. There is no development on 2.6.32 any more -- only
merges of upstream longterm 2.6.32.y -- so I think that would be
reasonably safe.
-or-
Use git://xenbits.xen.org/linux-pvops.git branch master which is what
would normally be at xen.git xen/stable-2.6.32.x i.e. it''s is the
tested
branch. This is actually where the tester pushes to, the kernel.org tree
used to be automatically mirrored but that stopped working after the
kernel.org compromise.
Ian.