Re: git suggestion of fix to Amon

Javier Juan Martínez Cabezón <[email protected]> Fri, 2 Aug 2013 13:13:35 +0200
Newsgroups gmane.linux.rsbac
Message-ID <CAD98N_Fe2zN-ZhMsLwvLip=yKTXhQozGqm_Ysh0-1ZJZzW72gw@mail.gmail.com>
No, It's a bz2 kernel. Kernel runs but makes and OOPS when the
configure of xz-utils ebuild while are making some particular tests.

I

2013/8/2, Jens Kasten <[email protected]>:
> Did you configure your kernel compressed as xz?
>
> Am Freitag, den 02.08.2013, 11:37 +0200 schrieb Javier Juan Martínez
> Cabezón:
>> you are too lucky, mine 3.10 one suicides itself, xz-utils compilation
>> indigestion.
>>
>> 2013/8/2, Jens Kasten <[email protected]>:
>> > kernel 3.10.4 is running :)
>> >
>> > Am Freitag, den 02.08.2013, 09:30 +0200 schrieb Javier Juan Martínez
>> > Cabezón:
>> >> Ok, Amon. Thank you.
>> >>
>> >> 2013/8/2, Amon Ott <[email protected]>:
>> >> > Am 01.08.2013 18:20, schrieb Amon Ott:
>> >> >> Am 01.08.2013 16:02, schrieb Javier Juan Martínez Cabezón:
>> >> >>> Or this:
>> >> >>>
>> >> >>> http://git.661346.n2.nabble.com/Large-repo-and-pack-packsizelimit-td7523383.html
>> >> >>
>> >> >> Thanks for the links, they are interesting. I had already tested
>> >> >> with
>> >> >> several options, just tried some more from this link. However, no
>> >> >> success. I still cannot clone that repo.
>> >> >
>> >> > If you do not need to see the whole linux kernel history, a "shallow"
>> >> > clone works, e.g.:
>> >> >
>> >> > git clone --depth 100 git://rsbac.org/linux-3.10.y.git
>> >> >
>> >> > See "git help clone" for further restrictions:
>> >> >   --depth <depth>
>> >> >    Create a shallow clone with a history truncated to the specified
>> >> >    number of revisions. A shallow repository has a number of
>> >> > limitations
>> >> >    (you cannot clone or fetch from it, nor push from nor into it),
>> >> > but
>> >> > is
>> >> >    adequate if you are only interested in the recent history of a
>> >> > large
>> >> >    project with a long history, and would want to send in fixes as
>> >> >    patches.
>> >> >
>> >> > I will keep trying to work around the git problem. git people also
>> >> > seem
>> >> > to be aware of it.
>> >> >
>> >> > Amon.
>> >> > --
>> >> > http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22
>> >> > _______________________________________________
>> >> > rsbac mailing list
>> >> > [email protected]
>> >> > http://www.rsbac.org/mailman/listinfo/rsbac
>> >> >
>> >> _______________________________________________
>> >> rsbac mailing list
>> >> [email protected]
>> >> http://www.rsbac.org/mailman/listinfo/rsbac
>> >
>> >
>> > _______________________________________________
>> > rsbac mailing list
>> > [email protected]
>> > http://www.rsbac.org/mailman/listinfo/rsbac
>> _______________________________________________
>> rsbac mailing list
>> [email protected]
>> http://www.rsbac.org/mailman/listinfo/rsbac
>
>
> _______________________________________________
> rsbac mailing list
> [email protected]
> http://www.rsbac.org/mailman/listinfo/rsbac