From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, tali@admingilde.org
Subject: Re: [PATCH libata-dev-2.6:upstream] libata EH document update
Date: Wed, 28 Sep 2005 12:19:14 -0400 [thread overview]
Message-ID: <433AC282.6010000@pobox.com> (raw)
In-Reply-To: <20050926022847.GA9724@htj.dyndns.org>
Tejun Heo wrote:
> Hello, Jeff.
>
> Here's DocBook'fied libata_eh document. Sorry it took so long.
thanks, applied.
> To whine a little bit, I still think it's better to go plain text
> with ata docs under Documentation/ata. I don't really see the
> benefits of DocBook as it currently stands. It's so much less
> accessible. make pdf/ps docs still don't work and although it's been
> broken for quite a while now, nobody really cares.
It depends on your distro whether it works or not :(
For me, I just 'make xmldocs' then use db2pdf to convert the documents,
since xmlto fails miserably.
> One benefit of using DocBook is integrating docs generated from
> comments with the rest of template but I think such generated content
> can (maybe should) stay separate from other stuff. I think the
> generated content and the rest won't stay synchronized for very long
> considering the rate of change, lazy doc updates and even less
> interest in DocBook docs. Okay, enough whining.
>
> For libata_eh doc, I just created a <sect1> which contains the whole
> thing. I thought about separating out origins of commands and stuff
> into separate chapters so that the structure of the document is more
> consistent, but the contents were too little to be spread out and they
> are describing in EH centric way, so I just left all in one chapter.
>
> I'm thinking about attaching ata_exceptions doc at the end of this
> DocBook file as a separate supplementary chapter. What do you think?
Sounds good to me, though I think it works best when placed before the
chapters for the individual drivers.
Jeff
next prev parent reply other threads:[~2005-09-28 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 2:28 [PATCH libata-dev-2.6:upstream] libata EH document update Tejun Heo
2005-09-28 16:19 ` Jeff Garzik [this message]
2005-09-28 16:25 ` Randy.Dunlap
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=433AC282.6010000@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=tali@admingilde.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.