From: "Francisco Blas Izquierdo Riera (klondike)" <klondike@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] /etc/conf.d/hwclock and /etc/conf.d/adjkerntz
Date: Tue, 13 Sep 2011 00:42:03 +0200 [thread overview]
Message-ID: <4E6E8ABB.5050909@gentoo.org> (raw)
In-Reply-To: <CAPzO=NzUdghPsFW0wo5zbXWFfFf+3-zW7pcAHoKSmvhn_xKQog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
El 12/09/11 16:29, Sven Vermeulen escribió:
> My main concern here is that there will be a place where the number of
> choices is too big.
When that happens we can always split the document and create new per
choice ones, that's what is done with the handbooks for example, true?
> Also, you'll risk getting a higher frequency on
> bug reports on such paragraphs.
Well I have to disagree with that, less more review documents will have
less bug reports than many less reviewed ones.
> Think for instance bootloaders, how
> would we deal with guides there?
I think the way we do is ok, I mean having different parts for different
bootloaders.
> I'm sure we do not want to generate
> separate guides for just all this sort of stuff (and then use
> keywords)...
We don't.
> What about making it generic (edit your clock management configuration
> like, like /etc/conf.d/hwclock on ... )?
Well this particular case offers the deal that the configuration to
change is the same (just in different places), the problem with generic
definitions is that they tend to confuse users, and if we specify a
single alternative then users of the others will get even more confused.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-09-12 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 22:26 [gentoo-doc] /etc/conf.d/hwclock and /etc/conf.d/adjkerntz Francisco Blas Izquierdo Riera (klondike)
2011-09-12 14:29 ` Sven Vermeulen
2011-09-12 22:42 ` Francisco Blas Izquierdo Riera (klondike) [this message]
2011-09-13 12:11 ` Sven Vermeulen
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=4E6E8ABB.5050909@gentoo.org \
--to=klondike@gentoo.org \
--cc=gentoo-doc@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox