From: Christian Faulhammer <opfer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [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 20:31:59 +0200 [thread overview]
Message-ID: <20071015203159.6b79ab71@gentoo.org> (raw)
In-Reply-To: <47137B11.1070003@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
Doug Goldstein <cardoe@gentoo.org>:
> Jonathan Adamczewski wrote:
> > Doug Goldstein wrote:
> >> That's what this commits review list feels like.
> > Nearly every suggestion (from Donnie and others) has been over some
> > issue that relates directly to either correctness or
> > maintainability. It doesn't matter if you can "rattle off
> > capabilities to a millimeter" - if they're not documented somewhere
> > (like, say, in the comments of the ebuild) then the maintainer that
> > comes after you gets to go and break it all over again.
> Correctness? Fine. Go ahead. Stick $(use_enable xvmc) into the ebuild.
> Do it. I dare you. Then try to compile.
> Guess what? When it blows up... that's called INcorrect. The opposite
> of the right thing.
You were kindly asked if is not possible to use, so why do you feel
attacked? Do a comment on it and everybody would be fine, even the
people that would have to maintain it some time in the future. If you
don't like the review process, just ignore it.
Reviews are not a way to show what kind of idiot the committer is, but
to improve the overall quality of the tree. Nothing more, nothing less.
> The maintainer who comes after me would be someone with a experience
> with the package. Some bumkin isn't going to come to maintain package
> XYZ unless they know or use the package, and guess what? That means
> experience.
Yes, and the same goes for GNU Emacs, I needed some time to figure out
what all those things did and I broke it several times because I tried
to be clever. Now we documented it and I think everyone coming after us
will have a less hard time to understand it. Better document it, you
never know what happens.
V-Li
--
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
<URL:http://www.faulhammer.org/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-15 18:46 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 [this message]
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
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=20071015203159.6b79ab71@gentoo.org \
--to=opfer@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