On Sun, Apr 24, 2016 at 12:14 PM, Daniel Eischen
wrote:
> On Sun, 24 Apr 2016, Warner Losh wrote:
>
> On Sun, Apr 24, 2016 at 6:34 AM, Daniel Eischen
>> wrote:
>>
>> On Sat, 23 Apr 2016, Warner Losh wrote:
>>>
>>> On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
>>>
wrote:
[CC tri
On Sun, 24 Apr 2016, Warner Losh wrote:
On Sun, Apr 24, 2016 at 6:34 AM, Daniel Eischen
wrote:
On Sat, 23 Apr 2016, Warner Losh wrote:
On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
wrote:
[CC trimmed]
On Fri, 22 Apr 2016, Warner Losh wrote:
I personally will be refraining from enga
On Sun, Apr 24, 2016 at 6:34 AM, Daniel Eischen
wrote:
> On Sat, 23 Apr 2016, Warner Losh wrote:
>
> On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
>> wrote:
>>
>> [CC trimmed]
>>>
>>> On Fri, 22 Apr 2016, Warner Losh wrote:
>>>
>>>
I personally will be refraining from engaging further. I
> On Apr 24, 2016, at 05:34, Daniel Eischen wrote:
>
>> On Sat, 23 Apr 2016, Warner Losh wrote:
>>
>> On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
>> wrote:
>>
>>> [CC trimmed]
>>>
On Fri, 22 Apr 2016, Warner Losh wrote:
I personally will be refraining from engaging
On Sat, 23 Apr 2016, Warner Losh wrote:
On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
wrote:
[CC trimmed]
On Fri, 22 Apr 2016, Warner Losh wrote:
I personally will be refraining from engaging further. I plan on seeing
what gaps there are by adding support to NanoBSD for packages. I'll b
On Sat, Apr 23, 2016 at 7:51 AM, Daniel Eischen
wrote:
> [CC trimmed]
>
> On Fri, 22 Apr 2016, Warner Losh wrote:
>
>>
>> I personally will be refraining from engaging further. I plan on seeing
>> what gaps there are by adding support to NanoBSD for packages. I'll be
>> busy
>> with that. In talk