From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: list purpose. was: Re: [gentoo-dev] Re: gentoo-x86 commit in app-forensics/memdump: memdump-1.0.1.ebuild ChangeLog
Date: Mon, 5 Jan 2009 11:29:21 -0500 [thread overview]
Message-ID: <20090105162921.GA15481@aerie.halcy0n.com> (raw)
In-Reply-To: <200901052215.42529.dragonheart@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Daniel Black <dragonheart@gentoo.org> said:
> I'm not sure I want to see this list being a QA list for commits.
>
> If there is a commit that raises an interesting question for everyone sure put
> it here.
>
> Otherwise please take up QA faults with the author or devrel if you think they
> are consistantly under-standard.
I'm pretty sure this has come up before... The developer list is the
best place for us to do peer review, since it not only helps the person
that is being reviewed, but also helps other developers at the same
time since they can see issues and how to correct them.
My 2c would be that if you don't want to see them to set up a filter.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-05 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LJcf9-00025P-UZ@stork.gentoo.org>
2009-01-05 0:07 ` [gentoo-dev] Re: gentoo-x86 commit in app-forensics/memdump: memdump-1.0.1.ebuild ChangeLog Torsten Veller
2009-01-05 8:25 ` Nirbheek Chauhan
2009-01-06 9:08 ` Peter Volkov
2009-01-05 11:15 ` list purpose. was: " Daniel Black
2009-01-05 16:29 ` Mark Loeser [this message]
2009-01-05 23:50 ` [gentoo-dev] Re: list purpose. was: " Duncan
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=20090105162921.GA15481@aerie.halcy0n.com \
--to=halcy0n@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