Federico Bruni writes:
> Il giorno ven 18 set 2015 alle 23:51, Trevor Daniels
> ha scritto:
>>> What have you tried? Who is doing what in regard to a mail server?
>>> Are
>>> we waiting from anybody from Savannah?
>>
>> I myself don't have the skills required to set up servers. It was
>> Fede
Il giorno ven 18 set 2015 alle 23:51, Trevor Daniels
ha scritto:
What have you tried? Who is doing what in regard to a mail server?
Are
we waiting from anybody from Savannah?
I myself don't have the skills required to set up servers. It was
Federico and Josiah who were working on this as
David Kastrup wrote Friday, September 18, 2015 9:46 PM
> "Trevor Daniels" writes:
>
>> At present the attempts to install a working mail server did not
>> succeed, and I have seen no progress in resolving this for a couple of
>> weeks.
>
> What have you tried? Who is doing what in regard to a
"Trevor Daniels" writes:
> David Kastrup wrote Tuesday, September 15, 2015 2:39 PM
>
>> Apropos issues: any news about our Allura installation? What is holding
>> up the migration of the issues there? The https certificate is not per
>> se a problem since developers can tell their browser expli
David Kastrup wrote Tuesday, September 15, 2015 2:39 PM
> Apropos issues: any news about our Allura installation? What is holding
> up the migration of the issues there? The https certificate is not per
> se a problem since developers can tell their browser explicitly to
> accept a certificate
On 15/09/15 15:27, James wrote:
>
> Hello,
>
> On 15/09/15 13:57, Phil Holmes wrote:
>> A comment and a question about the status field of the issues list.
>>
>> Comment: with Google code, the status was automatically set to "Accepted"
>> for issues manually entered by a registered user. I see
Colin Campbell writes:
> On 2015-09-15 08:36 AM, Phil Holmes wrote:
>>
>> Don't really like the idea of an undefined status. If we don't go
>> for "invalid", perhaps another "closed" status of "abandoned" would
>> be better.
>>
>> --
>> Phil Holmes
>>
>
> Abandoned patches are a bit different f
On 2015-09-15 08:36 AM, Phil Holmes wrote:
Don't really like the idea of an undefined status. If we don't go for
"invalid", perhaps another "closed" status of "abandoned" would be
better.
--
Phil Holmes
Abandoned patches are a bit different from closed issues, IMO. It's
absolutely nece
Simon Albrecht writes:
> If a patch has been abandoned for lack of skill or time, Status should
> go back to Accepted. Though it can’t be said in general: if it has
> been abandoned because the developer decided it didn’t make sense, or
> if it has become obsolete through other development, then
Am 15.09.2015 um 15:39 schrieb David Kastrup:
Phil Holmes writes:
A comment and a question about the status field of the issues list.
Comment: with Google code, the status was automatically set to "Accepted"
for issues manually entered by a registered user. I see no reason for not
continuing
hello,
On 15/09/15 16:50, David Kastrup wrote:
> Simon Albrecht writes:
>
>> If a patch has been abandoned for lack of skill or time, Status should
>> go back to Accepted. Though it can’t be said in general: if it has
>> been abandoned because the developer decided it didn’t make sense, or
>> if
- Original Message -
From: "James"
To:
Sent: Tuesday, September 15, 2015 3:27 PM
Subject: Re: Issues list status
Hello,
On 15/09/15 13:57, Phil Holmes wrote:
A comment and a question about the status field of the issues list.
Comment: with Google code, the
Phil Holmes writes:
> A comment and a question about the status field of the issues list.
>
> Comment: with Google code, the status was automatically set to "Accepted"
> for issues manually entered by a registered user. I see no reason for not
> continuing this policy, but it does mean that bu
Hello,
On 15/09/15 13:57, Phil Holmes wrote:
> A comment and a question about the status field of the issues list.
>
> Comment: with Google code, the status was automatically set to "Accepted"
> for issues manually entered by a registered user. I see no reason for not
> continuing this policy,
A comment and a question about the status field of the issues list.
Comment: with Google code, the status was automatically set to "Accepted"
for issues manually entered by a registered user. I see no reason for not
continuing this policy, but it does mean that bug squad members (and
anyone el
15 matches
Mail list logo
