public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new developers' keyword requests
Date: Fri, 20 May 2016 16:00:02 +0200	[thread overview]
Message-ID: <20160520160002.2aace085@wim.fritz.box> (raw)
In-Reply-To: <e2cc6cca-878e-86f0-2576-555f64f454c2@gentoo.org>

On Thu, 19 May 2016 18:36:22 -0700
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? If said arches are already supported in Gentoo
> I see little problem with that, especially if they intend on being
> part of the arch testing team for that arch or have access to the
> hardware.

I am not talking about adding architecture keywords to profiles/.
I am talking about adding architecture keywords to ebuilds.


Regards,
     jer


  parent reply	other threads:[~2016-05-20 14:00 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 [this message]
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     ` [gentoo-dev] " Jeroen Roovers

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=20160520160002.2aace085@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