On Sat, 2024-01-27 at 16:17 -0800, Chris Hanson wrote:
> It looks like there are CVS commits that haven’t made it to the
> GitHub mirror yet.
>
> Anyone know what’s up with that?
>
> -- Chris
>
The Mercurial mirror also hasn't been updated for a week.
Ngā mihi,
Lloyd
It looks like there are CVS commits that haven’t made it to the GitHub mirror
yet.
Anyone know what’s up with that?
-- Chris
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/xlint/lint1/t_integration:lex_integer_ilp32
usr.bin/xlint/lint1/t_integration:msg_218
The above tests failed in each of the last 4 test runs, and passed in
at
On Fri, Jan 26, 2024 at 09:09:30PM +0100, Adam wrote:
> Simple and elegant. No hacks involved.
Because the declaration in the relevant header is already there, and
the order does not matter. But the #ifdef around the declaration needs
to do the right thing. No need to move things around and its
Date:Fri, 26 Jan 2024 21:09:30 +0100
From:Adam
Message-ID: <7be03ef0-a516-4102-951a-be8a0d468...@netbsd.org>
| Why not just change the order?
Christos has done that now, so I guess that more or less "fixes" the
issue.
I didn't want to do it that way, as it still
On Sat, Jan 27, 2024 at 03:33:06PM +0700, Robert Elz wrote:
> Now that Christos moved the function around, that declaration in the
> header is just noise, and could be removed.
Yes, that would be consistent then (but isn't it against the new style
rules?)
Martin
Date:Sat, 27 Jan 2024 09:11:58 +0100
From:Martin Husemann
Message-ID: <20240127081158.gb16...@mail.duskware.de>
| Because the declaration in the relevant header is already there,
Now that Christos moved the function around, that declaration in the
header is just
Updating src tree:
P src/distrib/sets/lists/base/mi
P src/distrib/sets/lists/tests/mi
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/etc/mtree/NetBSD.dist.base
P src/external/mit/xorg/server/xorg-server.old/Makefile.servermod
P
> Now that Christos moved the function around, that declaration in the
> header is just noise, and could be removed.
Thank you for fixing this.
Adam
