From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new developers' keyword requests
Date: Fri, 20 May 2016 15:11:21 +0200 [thread overview]
Message-ID: <a86421c1-632e-a2ce-3f9b-331916317572@gentoo.org> (raw)
In-Reply-To: <550ab3a6-1a4b-fa19-b111-5cbf82fe597e@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]
On 05/20/2016 02:38 PM, Kristian Fiskerstrand wrote:
> On 05/20/2016 03:36 AM, Daniel Campbell wrote:
>> On 05/19/2016 07:51 AM, Jeroen Roovers wrote:
>
>
> keywording for a new arch should normally only be done when necessary,
> mainly if it is a direct dependency of another package. There is no need
> to keywor it for an arch until it has been tested on that arch by some
> user / developer ... certainly not because some committing developer
> think it is nice to have all arches listed just in case.
>
I should actually elaborate on this (in addition to fixing some spelling
errors..), something to the line of "There is no need to keyword it for
an arch until it is being _used_ by some user/developer on that arch"
--
Kristian Fiskerstrand
OpenPGP certificate reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-05-20 13:11 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 [this message]
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 ` [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=a86421c1-632e-a2ce-3f9b-331916317572@gentoo.org \
--to=k_f@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