On Mon, Jan 20, 2014 at 4:46 PM, Rich Freeman wrote:
> On Mon, Jan 20, 2014 at 7:22 PM, Patrick Lauer wrote:
> >
> > Yey, we're allowed to sometimes do revert games, if we're asking nicely
> > ... and the only way to stop the revert game is for QA to stand down.
> > We're allowed to send strongl
On Mon, Jan 20, 2014 at 4:22 PM, Patrick Lauer wrote:
> On 01/20/2014 10:09 PM, Alan McKinnon wrote:
> > On 01/20/14 15:59, Rich Freeman wrote:
> >> On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman wrote:
> >>> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to
> suspend
> >>> peop
On Mon, Jan 20, 2014 at 7:22 PM, Patrick Lauer wrote:
>
> Yey, we're allowed to sometimes do revert games, if we're asking nicely
> ... and the only way to stop the revert game is for QA to stand down.
> We're allowed to send strongly-worded emails, but getting things baked
> into policy is too ra
On 01/20/2014 10:09 PM, Alan McKinnon wrote:
> On 01/20/14 15:59, Rich Freeman wrote:
>> On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman wrote:
>>> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to suspend
>>> people
>>>
>>> Whether this has actually happened is something that is q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/20/2014 06:54 PM, William Hubbs wrote:
> On Mon, Jan 20, 2014 at 07:18:46PM +0100, Alexander Berntsen
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 20/01/14 18:26, William Hubbs wrote:
>>> On Mon, Jan 20, 2014 at 02:23:2
On Sun, 2014-01-19 at 10:46 +0100, Ulrich Mueller wrote:
> Now what problem are we trying to solve? As I see it, it is mainly
> one of manpower, namely that some arch teams cannot keep up with
> stable requests, and I doubt that any technical solution will help
> to solve this. Introducing a "noarc
On Mon, Jan 20, 2014 at 07:18:46PM +0100, Alexander Berntsen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 20/01/14 18:26, William Hubbs wrote:
> > On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
> >> this has all been fairly ad-hoc in the past, so formalize it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/01/14 18:26, William Hubbs wrote:
> On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
>> this has all been fairly ad-hoc in the past, so formalize it in
>> the one place that impacts everyone -- profiles.desc.
> If it is policy, s
On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
> this has all been fairly ad-hoc in the past, so formalize it in the one place
> that impacts everyone -- profiles.desc.
> -mike
If it is policy, shouldn't it go in the dev manual rather than in this
file?
Given that, I have questio
On Monday 20 January 2014 04:16:23 Ulrich Mueller wrote:
> Sorting order is different from the present ekeyword. The part after
> the hyphen (or the empty string if there is no hyphen) should be used
> as primary key and the part before the hyphen as secondary key.
hmm, was unaware of that. shoul
On 01/20/14 15:59, Rich Freeman wrote:
> On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman wrote:
>> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to suspend
>> people
>>
>> Whether this has actually happened is something that is questionable;
>
> Not that this necessarily needs to
On Sun, Jan 19, 2014 at 9:54 PM, Tom Wijsman wrote:
> #gentoo-qa | @hwoarang: pretty sure diego had the powerzz to suspend
> people
>
> Whether this has actually happened is something that is questionable;
Not that this necessarily needs to make it into the GLEP, and I'm
still on the fenc
> On Mon, 20 Jan 2014, Mike Frysinger wrote:
> i finally got annoyed with the perl version (and its output and bugs
> and limitations) and wrote a new version. it's fairly modular (and
> has pretty good unittest coverage!?), so if we wanted to look at
> integrating it into portage or other too
13 matches
Mail list logo
