Hi Roy,
"Roy Marples" wrote:
> Module Name: src
> Committed By: roy
> Date: Wed Mar 11 21:33:38 UTC 2020
>
> Modified Files:
>
> src/lib/libcurses: initscr.c
>
> Log Message:
>
> curses: application should exit if initscr(3) fails
>
> POSIX defines this behaviour here:
> https://pu
On Wed, Mar 11, 2020 at 23:47:40 +, Roy Marples wrote:
> Module Name: src
> Committed By: roy
> Date: Wed Mar 11 23:47:40 UTC 2020
>
> Modified Files:
> src/lib/libcurses: erase.c
>
> Log Message:
> curses: Fix werase(3) wide character support
>
> We need to consider erasing
On Wed, Mar 11, 2020 at 7:22 AM Greg Troxel wrote:
>
> J. Hannken-Illjes writes:
>
> >> Forgot to add in the commit log, the changes have been pulled in from
> >> upstream openzfs.
> >>
> >> https://github.com/openzfs/zfs/commit/928e8ad47d3478a3d5d01f0dd6ae74a9371af65e#diff-9fd6b453f8153161abe072
Le 27/02/2020 à 01:36, Simon Burge a écrit :
> "Maxime Villard" wrote:
>
>> Module Name: src
>> Committed By:maxv
>> Date:Wed Feb 26 18:00:12 UTC 2020
>>
>> Modified Files:
>>
>> src/sys/ufs/ufs: ufs_vnops.c
>>
>> Log Message:
>>
>> Zero out the padding in 'd_namlen',
In article <20200311023318.c6a7ff...@cvs.netbsd.org>,
Roy Marples wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: roy
>Date: Wed Mar 11 02:33:18 UTC 2020
>
>Modified Files:
> src/external/bsd/blacklist/bin: blacklistd.c
>
>Log Message:
>blacklist: Don't remove a ruleset if
On Wed, Mar 11, 2020 at 08:22:26AM -0400, Greg Troxel wrote:
> This seems to be hard to figure out. Is there someplace in the tree
> that says what our upsream is, and what theirs is, and how all of the
> various trees out there relate? And how we should be sending things,
> and getting things?
In article <20200311021208.bfb5cf...@cvs.netbsd.org>,
Roy Marples wrote:
>-=-=-=-=-=-
>
>Module Name: src
>Committed By: roy
>Date: Wed Mar 11 02:12:08 UTC 2020
>
>Modified Files:
> src/external/bsd/blacklist/bin: blacklistd.c conf.c
> src/external/bsd/blacklist/lib: bl.c
>
J. Hannken-Illjes writes:
>> Forgot to add in the commit log, the changes have been pulled in from
>> upstream openzfs.
>>
>> https://github.com/openzfs/zfs/commit/928e8ad47d3478a3d5d01f0dd6ae74a9371af65e#diff-9fd6b453f8153161abe0728c449e6505R4386
>
> This is NOT our upstream --
This seems to b
