On 4/21/2012 5:28 PM, Eitan Adler wrote:
> On 21 April 2012 20:25, Eitan Adler wrote:
>> If I had to guess freebsd-python takes all ports with py- and someone
>> manually did a kick-aa on the port to force the PR over to you. The
>> sequence of changes does seem a bit odd.
>
> Actually, taking a
ports/167178: Update port: security/py-keyring Upgrade to version
0.9
On 4/21/2012 2:55 PM, Michael Scheidell wrote:
>
>
> On 4/21/12 5:50 PM, Douglas Thrift wrote:
>> Huh? Don't know why it decided I wasn't the maintainer and then emailed
>> me since I was the main
On 21 April 2012 20:25, Eitan Adler wrote:
> If I had to guess freebsd-python takes all ports with py- and someone
> manually did a kick-aa on the port to force the PR over to you. The
> sequence of changes does seem a bit odd.
Actually, taking a slightly closer look: it seems the email address
y
On 21 April 2012 20:21, Douglas Thrift wrote:
> Hello Michael,
>
> I am well aware of how PRs are supposed to work.
>
> I was talking about "Fix category (submitter is not maintainer) (via the
> GNATS Auto Assign
> Tool)" and the email sent to me asking to approve (because I am actually
> the mai
On 4/21/2012 2:55 PM, Michael Scheidell wrote:
>
>
> On 4/21/12 5:50 PM, Douglas Thrift wrote:
>> Huh? Don't know why it decided I wasn't the maintainer and then emailed
>> me since I was the maintainer.
> don't worry. maintainer isn't the same field as 'Responsible'
> Responsible is someone
Synopsis: Update port: security/py-keyring Upgrade to version 0.9
State-Changed-From-To: feedback->open
State-Changed-By: jgh
State-Changed-When: Sat Apr 21 21:53:52 UTC 2012
State-Changed-Why:
I'll take this. Fix class, state and submitter information.
Class-Changed-From-To: change-request->ma
On 4/21/12 5:50 PM, Douglas Thrift wrote:
Huh? Don't know why it decided I wasn't the maintainer and then emailed
me since I was the maintainer.
don't worry. maintainer isn't the same field as 'Responsible'
Responsible is someone with GNATS access, or the default group until one
of the c
The following reply was made to PR ports/167178; it has been noted by GNATS.
From: Douglas Thrift
To: bug-follo...@freebsd.org
Cc:
Subject: Re: ports/167178: Update port: security/py-keyring Upgrade to version
0.9
Date: Sat, 21 Apr 2012 14:40:54 -0700
Huh? Don't know why it decided I w
The following reply was made to PR ports/167178; it has been noted by GNATS.
From: Edwin Groothuis
To: doug...@douglasthrift.net
Cc: bug-follo...@freebsd.org
Subject: Re: ports/167178: Update port: security/py-keyring Upgrade to version
0.9
Date: Sat, 21 Apr 2012 21:30:37 UT
Maintainer of
Synopsis: Update port: security/py-keyring Upgrade to version 0.9
State-Changed-From-To: open->feedback
State-Changed-By: edwin
State-Changed-When: Sat Apr 21 21:30:41 UTC 2012
State-Changed-Why:
Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
http://www.freebsd.org/cgi/query-pr.c
Synopsis: Update port: security/py-keyring Upgrade to version 0.9
Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python
Responsible-Changed-By: edwin
Responsible-Changed-When: Sat Apr 21 21:30:32 UTC 2012
Responsible-Changed-Why:
freebsd-python@ wants this port PRs (via the GNATS Auto A
11 matches
Mail list logo
