linux-kernel - Re: [PATCH 1/7] lguest: documentation pt I: Preparation

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: <20070724170028.42c6bd8d@the-village.bc.nu>
Date:	Tue, 24 Jul 2007 17:00:28 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	corbet@....net (Jonathan Corbet)
Cc:	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 1/7] lguest: documentation pt I: Preparation

> P.S. I am currently considering a no-limericks policy for the LWN quote
> of the week.

The LWN quote of the week
Is I think rather weak
No poems allowed
To rise from the crowd
Its future looks terribly bleak

More seriously the documentation looks good, and it definitely wants a
date/release clearly mentioning so people know when it is obsolete

> Advantage:  it does keep the source code + doc text together.
> Martin (former kernel-doc maintainer) was going to come up with
> some way to do this, but he abandoned it. 

It's not clear to me how you then format the extracted material. It
doesn't really fit the kernel-doc idea of formats. It would probably be
far easier to teach a seperate tool to rip clearly marked blocks into
ASCII documentation files for that purpose

Alan
-
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/