From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: list purpose. was: Re: Re: gentoo-x86 commit in app-forensics/memdump: memdump-1.0.1.ebuild ChangeLog
Date: Mon, 5 Jan 2009 23:50:15 +0000 (UTC) [thread overview]
Message-ID: <pan.2009.01.05.23.50.15@cox.net> (raw)
In-Reply-To: 20090105162921.GA15481@aerie.halcy0n.com
Mark Loeser <halcy0n@gentoo.org> posted
20090105162921.GA15481@aerie.halcy0n.com, excerpted below, on Mon, 05 Jan
2009 11:29:21 -0500:
> 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.
Seconded. This is specifically a technical list (project is otherwise),
and I'm not a dev but learn a lot from those posts, which are after all
technical and you couldn't get more gentoo-dev topic-wise.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2009-01-05 23:55 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
2009-01-05 23:50 ` Duncan [this message]
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=pan.2009.01.05.23.50.15@cox.net \
--to=1i5t5.duncan@cox.net \
--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