From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new developers' keyword requests
Date: Sat, 21 May 2016 11:01:58 +0200 [thread overview]
Message-ID: <20160521110158.495e53fa@wim.fritz.box> (raw)
In-Reply-To: <CAEdQ38GVspO5xTaf9yDAHHKFTj3QYXT=kG-wBqi-k+YiAAE8_w@mail.gmail.com>
On Fri, 20 May 2016 21:47:56 -0700
Matt Turner <mattst88@gentoo.org> wrote:
> On Thu, May 19, 2016 at 6:36 PM, Daniel Campbell <zlg@gentoo.org>
> wrote:
> > To make sure I understand what you're getting at, are you saying
> > some devs get on board and then request to add keywords to packages
> > that they already maintain?
>
> No, you've misunderstood.
>
> He's saying people add new packages and then speculatively add
> keywords for a bunch of architectures that they haven't tested.
No, that's already covered very well in the quizzes and devmanual.
What I mean is keyword requests of the type: "Hi, I maintain this
package now, and I'm very excited about it, so can I have these random
keywords added, please?"
I have plenty of examples of such keyword requests collected over the
years; anyone should be able to find them easily.
Regards,
jer
prev parent reply other threads:[~2016-05-21 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:51 [gentoo-dev] new developers' keyword requests Jeroen Roovers
2016-05-19 15:00 ` Mike Gilbert
2016-05-20 1:36 ` Daniel Campbell
2016-05-20 12:38 ` Kristian Fiskerstrand
2016-05-20 13:11 ` Kristian Fiskerstrand
2016-05-20 13:34 ` M. J. Everitt
2016-05-20 13:20 ` Daniel Campbell
2016-05-20 14:00 ` Jeroen Roovers
2016-05-21 2:09 ` Ian Delaney
2016-05-21 2:35 ` Sam Jorna
2016-05-21 4:47 ` Matt Turner
2016-05-21 6:41 ` Daniel Campbell
2016-05-21 7:08 ` [gentoo-dev] " Duncan
2016-05-21 9:01 ` Jeroen Roovers [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=20160521110158.495e53fa@wim.fritz.box \
--to=jer@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