public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv: ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild mythtv-0.21_pre14480-r1.ebuild
Date: Mon, 15 Oct 2007 15:09:43 -0700	[thread overview]
Message-ID: <20071015220943.GK23990@supernova> (raw)
In-Reply-To: <4713D43A.9080107@gentoo.org>

On 16:57 Mon 15 Oct     , Doug Goldstein wrote:
> I still stand by my original feeling that we'd better the community NOT
> only the developers doing the commits by updating the devmanual, which
> is accessible to all developers and all users in the Gentoo community.
> In addition to updating and cleaning up repoman checks, which is a tool
> that everyone in the community can use. This is versus individual
> examples in random ebuilds in random e-mails that all have almost an
> identical subject on the mailing list.
> 
> The commits review is flawed because if we're not documenting this stuff
> in one central place, then when new developers join. The same lessons
> have to be learned over and over again.

Doing the review helps us figure out what the common issues are, so we 
actually know what's worth documenting. I've had in mind all along 
getting common issues into docs and into repoman, which is why I wrote 
the original quoting patch.

Also, just because something is documented doesn't mean people do it. 
Furthermore, just because a doc says "write code without bugs" doesn't 
mean people are physically capable of doing so. More eyes on the code 
can never hurt.

Thanks,
Donnie
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-10-15 22:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IgPfK-0005R4-Tw@stork.gentoo.org>
2007-10-13  0:44 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv: ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild mythtv-0.21_pre14480-r1.ebuild Donnie Berkholz
2007-10-14  4:12   ` Doug Goldstein
2007-10-14  4:50     ` Donnie Berkholz
2007-10-14 12:02       ` [gentoo-dev] " Steve Long
2007-10-15 14:16       ` [gentoo-dev] " Doug Goldstein
2007-10-15 14:25         ` Jonathan Adamczewski
2007-10-15 14:37           ` Doug Goldstein
2007-10-15 18:31             ` Christian Faulhammer
2007-10-15 21:00               ` Doug Goldstein
2007-10-16 10:09                 ` Marijn Schouten (hkBst)
2007-10-15 19:14             ` Alec Warner
2007-10-15 20:57               ` Doug Goldstein
2007-10-15 22:09                 ` Donnie Berkholz [this message]
2007-10-16  1:17                 ` Ryan Hill
2007-10-16 23:04               ` Drake Wyrm
2007-10-15 20:57         ` [gentoo-dev] " Steve Long

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=20071015220943.GK23990@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