Quoting Casey Schaufler ([email protected]):
> Serge E. Hallyn wrote:
> > Quoting Casey Schaufler ([email protected]):
> >
> >> Serge E. Hallyn wrote:
> >>
> >>> Quoting Casey Schaufler ([email protected]):
> >>> Sorry, the c/r tree is at:
> >>>
> >>> git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git
> >>>
> >>>
> >> The four patches from 08/28 (2-5) and the two from 09/03
> >> are not happy applying to this tree. Am I missing a patch?
> >>
> >>
> >
> > There was this patch which was 1/5
> >
> > https://lists.linux-foundation.org/pipermail/containers/2009-August/020212.html
> >
> > But there have also been some changes since that posting to the
> > git tree. You could rewind the git tree to the state it was in
> > on aug 28, but I'll need to forward-port my patches anyway, so
> > let me do that this afternoon and resend the patchset.
> >
> >
>
> I figured it was something like that. Thank you.
Actually the patches still apply cleanly. But it turns out
that when you clone the linux-cr tree, it pulls the ckpt-v17
branch, and only the ckpt-v17 branch. It is hugely different
from the ckpt-v17-dev tree, which is the one you want. So
assuming you created a kernel tree by doing git clone
git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git (as opposed
to tweaking your .git/config in another git tree), then you
want to:
git fetch origin ckpt-v17-dev:ckpt-v17-dev
git checkout ckpt-v17-dev
The lsm c/r patches should apply cleanly there.
thanks,
-serge
_______________________________________________
Containers mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Devel mailing list
[email protected]
https://openvz.org/mailman/listinfo/devel
