lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20100924T104300-582@post.gmane.org>
Date:	Fri, 24 Sep 2010 08:54:10 +0000 (UTC)
From:	el es <el.es.cr@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Long maintenance kernel versions.

Geoffrey Said <geoffrey <at> 2x.com> writes:

1. You are top-posting.

2. To my non-developer naked eye it rather looks like - one of the developers
steps up and announces he's going to care for this particular kernel version,
and how long.

3. If it works and is adopted for your needs, why move ? Stick to it. Test new
kernels (apply your patches to them and test with your programs). Nobody knows
what you need, unless you tell them - or publish your patches. 

4. If you did that, you may publicly maintain the version you have selected for
as long as you need. That would be some way to GPL compliance too (IANAL). Move
to another kernel version only if it has a new feature that you actually need,
as bugfixes usually apply without need to change versions.

5. If more people like what you were doing, you may even become this stable
version maintainer.

Lukasz

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ