From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Features and documentation
Date: Tue, 27 Nov 2007 11:21:44 -0800 [thread overview]
Message-ID: <20071127192144.GP4368@supernova> (raw)
How the recent changes happened to allow USE flag descriptions in
metadata.xml (which I'm not taking any position on now) gave me an idea.
The Linux kernel requires that any needed documentation accompany all
changes requiring said documentation -- part of the source-code patch
must apply to the Documentation/ directory. Should we require that
before you commit any changes, you (or someone) write the documentation
for them and commit it or submit a patch at the same time?
To sum up: No undocumented changes.
Discuss.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-11-27 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:21 Donnie Berkholz [this message]
2007-11-27 19:25 ` [gentoo-dev] [RFC] Features and documentation Ciaran McCreesh
2007-11-27 19:36 ` Donnie Berkholz
2007-11-27 19:41 ` Ciaran McCreesh
2007-11-27 19:31 ` Doug Klima
2007-11-28 3:10 ` Alec Warner
2007-11-28 6:56 ` Rémi Cardona
2007-11-28 18:12 ` Zhang Le
2007-11-28 21:15 ` Donnie Berkholz
2007-11-29 0:43 ` Alec Warner
2007-11-29 1:01 ` Donnie Berkholz
2007-11-29 2:25 ` Alec Warner
2007-11-29 8:58 ` [gentoo-dev] " Christian Faulhammer
2007-11-29 13:57 ` [gentoo-dev] " Santiago M. Mola
2007-11-29 14:47 ` Doug Klima
2007-11-28 11:40 ` Marijn Schouten (hkBst)
2007-11-28 12:38 ` [gentoo-dev] " Duncan
2007-11-28 21:14 ` Donnie Berkholz
2007-11-28 21:33 ` Ciaran McCreesh
2007-11-29 0:29 ` Donnie Berkholz
2007-11-29 5:04 ` Duncan
2007-11-29 5:38 ` Donnie Berkholz
2007-11-29 18:06 ` Duncan
2007-11-29 19:29 ` Santiago M. Mola
2007-11-30 17:50 ` Duncan
2007-11-30 10:42 ` Steve Long
2007-11-30 17:42 ` Duncan
2007-11-28 19:02 ` 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=20071127192144.GP4368@supernova \
--to=dberkholz@gentoo.org \
--cc=gentoo-dev@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