> Date: Sun, 22 Dec 2019 10:24:01 +0100
> From: Maxime Villard
>
> You, Martin Christos and Taylor, are trying to change subject, find
> excuses, and are sending me irrelevant responses vaguely insinuating that
> I should revert my change only without addressing the additional concerns
>
On 23.12.2019 01:54, Roy Marples wrote:
> On 22/12/2019 22:24, Andrew Doran wrote:
>> NetBSD 9.99.29 - struct mount changed.
>
> Just curious - does our build software cope with 3 digit for the last
> number?
>
> Roy
At least from the __NetBSD_Version__ point of view there are 4 digits
unused,
Roy Marples wrote:
> On 22/12/2019 22:24, Andrew Doran wrote:
> > NetBSD 9.99.29 - struct mount changed.
>
> Just curious - does our build software cope with 3 digit for the last number?
https://twitter.com/needydev/status/1205585787095519234?s=20
--
Alex
On 22/12/2019 22:24, Andrew Doran wrote:
NetBSD 9.99.29 - struct mount changed.
Just curious - does our build software cope with 3 digit for the last number?
Roy
On 22.12.2019 23:27, Andrew Doran wrote:
> On Sat, Dec 21, 2019 at 05:23:23PM +, Alexander Nasonov wrote:
>
>> Andrew Doran wrote:
>>> Log Message:
>>> NetBSD 9.99.28 - cpu_data & UVM changes.
>>
>> Wow, you bump versions faster than I compile new releases. At this
>> pace, we'll get to
On Sat, Dec 21, 2019 at 05:23:23PM +, Alexander Nasonov wrote:
> Andrew Doran wrote:
> > Log Message:
> > NetBSD 9.99.28 - cpu_data & UVM changes.
>
> Wow, you bump versions faster than I compile new releases. At this
> pace, we'll get to 9.99.99 in a month or two ;-)
There are quite a few
Hi Joerg,
On Sun, Dec 22, 2019 at 01:27:44AM +0100, Joerg Sonnenberger wrote:
> On Fri, Dec 20, 2019 at 09:05:34PM +, Andrew Doran wrote:
> > Module Name:src
> > Committed By: ad
> > Date: Fri Dec 20 21:05:34 UTC 2019
> >
> > Modified Files:
> >
Le 21/12/2019 à 23:48, Christos Zoulas a écrit :
In article <15520611-7273-9567-33a4-ff2490b2e...@m00nbsd.net>,
Maxime Villard wrote:
Le 21/12/2019 à 00:05, Taylor R Campbell a écrit :
Security-team is not perfect. We're happy to discuss a better way to
disable filemon provisionally,
