public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] Handling of keywording bugs with only one arch
  @ 2010-04-04  9:38 99%         ` Petteri Räty
  0 siblings, 0 replies; 1+ results
From: Petteri Räty @ 2010-04-04  9:38 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

On 04/01/2010 11:28 PM, Jeroen Roovers wrote:
> On Sat, 27 Mar 2010 17:07:26 +0200
> Petteri Räty <betelgeuse@gentoo.org> wrote:
> 
>> On 03/27/2010 04:51 PM, Alex Alexander wrote:
>>>
>>> The only reason I don't really like this is because it breaks
>>> consistency. We have a ground rule, assign to maintainer, CC
>>> arch(es). Why make it more complicated? I have a feeling people
>>> will continue CCing arches out of habit.
> 
> +1.
> 
>> I don't think we should punish people for not doing it this way but
>> consider it the preferred way when doing new bugs. The initial point
>> here was to tell arches that assigning bugs directly to them is not
>> wrong.
> 
> Not wrong, just annoying for the arch team in question. Before
> resolving the bug report, you'd reassign to the maintainer and then
> close it? Why change it around twice, or even once for that matter?
> 
> 

I don't think I have ever suggested this or then I have been misunderstood.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2010-03-12 19:18     [gentoo-dev] Handling of keywording bugs with only one arch Petteri Räty
2010-03-27 14:26     ` Petteri Räty
2010-03-27 14:51       ` Alex Alexander
2010-03-27 15:07         ` Petteri Räty
2010-04-01 20:28           ` Jeroen Roovers
2010-04-04  9:38 99%         ` Petteri Räty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox