From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Christian Faulhammer <fauli@gentoo.org>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] EAPI 3 branch could use some reviewing
Date: Mon, 13 Apr 2009 16:59:23 +0100 [thread overview]
Message-ID: <20090413165923.7dd916bd@snowcone> (raw)
In-Reply-To: <20090413104944.54d4669f@terra.solaris>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Mon, 13 Apr 2009 10:49:44 +0200
Christian Faulhammer <fauli@gentoo.org> wrote:
> Ciaran McCreesh <ciaran.mccreesh@googlemail.com>:
> > On Sun, 12 Apr 2009 15:31:26 +0200
> > Christian Faulhammer <fauli@gentoo.org> wrote:
> > > The explanations of the slot operators are a bit hard to read,
> > > maybe rephrasing (and splitting in more sentences) is the way to
> > > go here.
> >
> > I suspect those're hard to read because people are expecting a
> > user-centric description of what they're for, rather than a package
> > manager centric description of how they behave.
>
> But also package manager coders are humans (at least the last time I
> checked), and apart from accuracy a technical documentation needs
> readability in its own special way. I wrote enough "scientific" and
> technical documents to be sure that small, easy to understand
> sentences are better.
Actually, looking at that... I don't really see anything off about it.
Which bit specifically don't you like?
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-13 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 20:14 [gentoo-pms] EAPI 3 branch could use some reviewing Ciaran McCreesh
2009-04-12 13:31 ` Christian Faulhammer
2009-04-12 15:43 ` Ciaran McCreesh
2009-04-13 8:49 ` Christian Faulhammer
2009-04-13 15:59 ` Ciaran McCreesh [this message]
2009-04-14 8:41 ` Christian Faulhammer
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=20090413165923.7dd916bd@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=fauli@gentoo.org \
--cc=gentoo-pms@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