On Fri, Nov 19, 2010 at 4:36 AM, Thomas Dziedzic <firstname.lastname@example.org> wrote:
> On Thu, Nov 18, 2010 at 5:31 PM, Seblu <email@example.com> wrote:
>> On Fri, Nov 19, 2010 at 12:22 AM, Thomas Dziedzic <firstname.lastname@example.org> wrote:
>>> On Thu, Nov 18, 2010 at 5:18 PM, Seblu <email@example.com> wrote:
>>> What's the difference between this and the kernel26-mainline package?
>> Mainline follow the mailine, mine follow only rc. For example, i also
>> have a kernel26-next. This give me the choice, at my computer start to
>> choose an another kernel which is a release candidate, without be in
>> redundant with kernel26 provided by arch developper.
>>> kernel26-rc used to exist, but it was later renamed to
>>> kernel26-mainline. So we should probably get rid of kernel26-rc also.
>> This was just a sharing of my work on my customs kernels packages. And
>> if my previous argument was not revelent, i will not post it again.
>> Sébastien Luttringer
> The mainline *is* the rc. look it up on kernel.org
You have not understand what i said. Maybe i was not clear.
my rc, only follow kernel mainline when it's tagged as a releasae
candidate. So my kernel will never have a 2.6.37 version for example.
But, to save you from a visceral reaction to the sight of this packet,
i will continue to use this packet for me after deletion