On 06/20/2017 11:08 PM, William A Rowe Jr wrote:
Sorry but I reraise my objection and veto worthless cpu cycles.
Hi Bill,
For posterity, can I get a succinct description of your technical
justification for this veto?
--Jacob
On Mon, Jun 26, 2017 at 3:14 PM, Jacob Champion wrote:
> On 06/20/2017 11:08 PM, William A Rowe Jr wrote:
>>
>> Sorry but I reraise my objection and veto worthless cpu cycles.
>
> For posterity, can I get a succinct description of your technical
> justification for this veto?
I have several.
*
Sorry Bill for the off-list mail now twice but either the list or
thunderbird's behavior with this list has changed. I'll assume the
former since I do not see the reply-to dev@ header anymore.
On 6/24/2017 10:02 AM, William A Rowe Jr wrote:
On Sat, Jun 24, 2017 at 12:49 AM, wrote:
Author: g
Hi Gregg,
sending publicly while you have a negotiation with your email client :)
On Mon, Jun 26, 2017 at 3:40 PM, Gregg Smith wrote:
>
> On 6/24/2017 10:02 AM, William A Rowe Jr wrote:
>>
>> On Sat, Jun 24, 2017 at 12:49 AM, wrote:
>>>
>>> Author: gsmith
>>> Date: Sat Jun 24 05:49:45 2017
>>>
On Mon, Jun 26, 2017 at 4:44 PM, William A Rowe Jr wrote:
>
> On Mon, Jun 26, 2017 at 3:40 PM, Gregg Smith wrote:
>>
>> On 6/24/2017 10:02 AM, William A Rowe Jr wrote:
>>>
>>> On Sat, Jun 24, 2017 at 12:49 AM, wrote:
>
>>> While we are at it, why even forking WIN32? If you want to prevent
>>> A
On Mon, Jun 26, 2017 at 11:51 PM, William A Rowe Jr wrote:
> On Mon, Jun 26, 2017 at 4:44 PM, William A Rowe Jr
> wrote:
>>
>> On Mon, Jun 26, 2017 at 3:40 PM, Gregg Smith wrote:
>>>
>>> On 6/24/2017 10:02 AM, William A Rowe Jr wrote:
On Sat, Jun 24, 2017 at 12:49 AM, wrote:
>>
On Mon, Jun 26, 2017 at 5:34 PM, Yann wrote:
> On Mon, Jun 26, 2017 at 11:51 PM, William A Rowe Jr
> wrote:
>> On Mon, Jun 26, 2017 at 4:44 PM, William A Rowe Jr
>> wrote:
>>>
>>> On Mon, Jun 26, 2017 at 3:40 PM, Gregg Smith wrote:
On 6/24/2017 10:02 AM, William A Rowe Jr wrote:
>>>
On Mon, Jun 26, 2017 at 5:43 PM, William A Rowe Jr wrote:
> On Mon, Jun 26, 2017 at 5:34 PM, Yann wrote:
>
>> What could be the "security blunders" with 404 vs 403?
>
> A 403 says "go away, you are denied". Hopefully modules are smart
> about that.
>
> A 404 says "no such resource". Modules such