From: Tom Wijsman <TomWij@gentoo.org>
To: williamh@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Tue, 21 Jan 2014 16:05:02 +0100 [thread overview]
Message-ID: <20140121160502.3c46c942@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20140120172613.GA6121@laptop.home>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Mon, 20 Jan 2014 11:26:13 -0600
William Hubbs <williamh@gentoo.org> wrote:
> If it is policy, shouldn't it go in the dev manual rather than in this
> file?
From a QA perspective, it would be nice to have the policy documentation
available in both locations; but as duplication would create out of date
copies, I suggest at the very least that we perhaps add a link that
refers to the devmanual page in the profiles.desc header. Maybe we can
make this more common practice in the future if people like the idea...
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-21 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 7:23 [gentoo-dev] new profiles.desc header documenting profile/keyword policy Mike Frysinger
2014-01-20 17:26 ` William Hubbs
2014-01-20 18:18 ` Alexander Berntsen
2014-01-20 18:54 ` William Hubbs
2014-01-20 19:40 ` Markos Chandras
2014-01-21 15:10 ` Tom Wijsman
2014-01-22 6:58 ` Mike Frysinger
2014-01-21 15:05 ` Tom Wijsman [this message]
2014-01-22 6:58 ` Mike Frysinger
2014-01-22 23:51 ` Tom Wijsman
2014-01-25 13:35 ` Markos Chandras
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=20140121160502.3c46c942@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=williamh@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