Date: Sun, 26 Aug 2012 20:38:01 +0100 From: Chris Rees <crees@FreeBSD.org> To: Doug Barton <dougb@freebsd.org> Cc: Steve Wills <swills@freebsd.org>, perl@freebsd.org Subject: Re: ports/171084: [PATCH] shells/p5-Shell-Perl: update to 0.0022 Message-ID: <CADLo838NesMVdmXgXTuXtqYF%2BOHovrfLSoRjPbcfsbf2DiDASg@mail.gmail.com> In-Reply-To: <503A794B.6060806@FreeBSD.org> References: <201208261840.q7QIe2nV047178@freefall.freebsd.org> <503A6F41.7070205@FreeBSD.org> <503A6FF9.5000207@FreeBSD.org> <503A70A7.30903@FreeBSD.org> <CADLo838o9B7yrHYJOZeQ-UzLnLf9NAMXWoit36BALW8mLfU%2BBA@mail.gmail.com> <503A794B.6060806@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 August 2012 20:30, Doug Barton <dougb@freebsd.org> wrote: > On 08/26/2012 12:03, Chris Rees wrote: >> On 26 August 2012 19:53, Doug Barton <dougb@freebsd.org> wrote: >>> On 08/26/2012 11:50, Steve Wills wrote: >>>> On 08/26/12 14:47, Doug Barton wrote: >>>>> Steve, >>>>> >>>>> Why do we have this sudden flood of PRs? >>>>> >>>> >>>> I'm bored and I got a local portscout instance working, so it's easier >>>> for me to see what's out of date. >>> >>> Ok .... but is there a way for you to relieve your boredom without >>> punishing us? :) Especially if you're going to end up taking the PR >>> anyway? >> >> Not really-- he's getting maintainer approval from a PR. >> >> If you know of any way to send a perl PR without it going via perl, please tell! > > The problem seems to be with the gnats auto-assigner: > > "^p5-" => "perl", > > Can we change that to be a list of ports that perl@ maintains? > > The alternative would be to set up a perl-bugs@ list. > Perhaps. Steve mentioned in a different reply to your email that he's working on changing priority; i.e. putting Submitter has GNATS access before perl@ wants this port's PRs. Hopefully that will be approved soon, but until then I fear procmail will be the only fix... Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838NesMVdmXgXTuXtqYF%2BOHovrfLSoRjPbcfsbf2DiDASg>