linux-kernel - Re: [PATCH] Documentation/Changes: phase out Changes file that hasn't changed

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]

Date:	Tue, 23 Jul 2013 20:47:25 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Aaro Koskinen <aaro.koskinen@....fi>
Cc:	Rob Landley <rob@...dley.net>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation/Changes: phase out Changes file that hasn't changed

On Tue, Jul 23, 2013 at 8:34 PM, Aaro Koskinen <aaro.koskinen@....fi> wrote:
> Hi,
>
> On Tue, Jul 23, 2013 at 06:10:01PM -0500, Rob Landley wrote:
>> On 07/23/2013 05:57:15 PM, Aaro Koskinen wrote:
>> >Is there any file describing the needed tools (and minimum versions) to
>> >_build_ the kernel? I agree that trying to describe such for the run-time
>> >userspace does not belong to the kernel tree, but the required/supported
>> >versions of build tools should be still maybe documented...
>>
>> Documentation/changes _is_ the file that describes the kernel's
>> build-time prerequisites.
>
> So, in that case the file should not be deleted.

Or, we could create a real required-packages.txt that isn't a decade out
of date (and poorly named), and have that in turn reference the arch
specific files with the arch specific data.

C'mon folks, have an open mind here.   Put yourself in the perspective
of the new user, and the issues that he/she faces.  Try and forget the
knowledge that you implicitly have gained of linux over time.   Pointing
these new users at this ancient Changes file is a good way to simply
drive them away.

We can do better.  I know we can.  And I know we all want that exact
same thing once we cut away all the BS.

Thanks,
Paul.
---

>
> A.
> --
> 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/
--
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/