All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [CORE-TOPIC] Documentation
Date: Mon, 13 Jul 2015 21:46:46 +0200	[thread overview]
Message-ID: <201507132146.47186.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20150713114509.14f1f866@lwn.net>

Am Montag, 13. Juli 2015, 19:45:09 schrieb Jonathan Corbet:
> On Mon, 13 Jul 2015 12:47:23 +0300
> 
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > I have counter suggestion:
> > * remove kernel-doc official status, remove generating scripts
> > 
> >   because it doesn't work,
> 
> kerneldoc does work, after a fashion.  It works well enough that people
> use it, and I hear about it quickly when somebody's comment change breaks
> the docs build.  I don't think we can remove it in the absence of
> something better.
Jonathan, do you keep an up-to-date copy of the generated files somewhere?
(I cannot get it to work out of the box on my machine)

> Creating "something better" is actually on my list of things to do.  The
> only problem is that I've had to buy a second 4TB drive to hold that list,
> so I don't know when I'll have time to think about it.
Where do you think are the major issues from your point of view? 

Would doxygen be "something better"? The kernel-doc style looks already quite 
similar.
Maybe the kernel should not reinvent everything :)




Thanks,
Peter

  reply	other threads:[~2015-07-13 19:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 22:38 [Ksummit-discuss] [CORE-TOPIC] Documentation Peter Hüwe
2015-07-12 23:15 ` Julia Lawall
2015-07-14 11:59   ` Mauro Carvalho Chehab
2015-07-13  9:47 ` Alexey Dobriyan
2015-07-13 16:01   ` Randy Dunlap
2015-07-13 16:37   ` Steven Rostedt
2015-07-13 16:46     ` David Woodhouse
2015-07-13 17:35       ` Steven Rostedt
2015-07-13 19:22         ` Peter Hüwe
2015-07-13 19:28       ` Peter Hüwe
2015-07-13 17:42     ` Jason Cooper
2015-07-13 18:11       ` Steven Rostedt
2015-07-14  3:56         ` Zefan Li
2015-07-13 19:25       ` Peter Hüwe
2015-07-13 22:10       ` Laurent Pinchart
2015-07-13 17:45   ` Jonathan Corbet
2015-07-13 19:46     ` Peter Hüwe [this message]
2015-07-14  2:36       ` Jonathan Corbet
2015-07-14  8:40         ` Laurent Pinchart
2015-07-14 11:19           ` Daniel Vetter
2015-07-14 12:43         ` Mauro Carvalho Chehab
2015-07-14 12:53           ` Jonathan Corbet
2015-07-14 13:57           ` Laurent Pinchart
2015-07-14  6:44       ` Johannes Berg
2015-07-13 19:20   ` Peter Hüwe
2015-07-13 23:01     ` Laurent Pinchart
2015-07-13 17:05 ` Lai Jiangshan
2015-07-13 17:42 ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201507132146.47186.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.