current-users  

Messages by Date

• 2024/06/29 Re: HEADS UP: plan to switch many ports over to GCC 12 soon Lloyd Parkes
• 2024/06/29 re: HEADS UP: plan to switch many ports over to GCC 12 soon matthew green
• 2024/06/29 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/29 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/29 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/29 Re: Automated report: NetBSD-current/i386 build failure Rin Okuyama
• 2024/06/29 Re: Automated report: NetBSD-current/i386 build failure Rin Okuyama
• 2024/06/29 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/28 daily CVS update output NetBSD source update
• 2024/06/27 daily CVS update output NetBSD source update
• 2024/06/26 daily CVS update output NetBSD source update
• 2024/06/26 Re: Odd kernel message Mike Pumford
• 2024/06/25 daily CVS update output NetBSD source update
• 2024/06/25 Re: Odd kernel message J. Hannken-Illjes
• 2024/06/25 Odd kernel message Mike Pumford
• 2024/06/24 daily CVS update output NetBSD source update
• 2024/06/23 daily CVS update output NetBSD source update
• 2024/06/22 daily CVS update output NetBSD source update
• 2024/06/22 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/22 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/21 Re: GCC 12 needs -std=c++11 Adam
• 2024/06/21 daily CVS update output NetBSD source update
• 2024/06/21 Re: GCC 12 needs -std=c++11 Christoph Badura
• 2024/06/21 GCC 12 needs -std=c++11 Adam
• 2024/06/20 daily CVS update output NetBSD source update
• 2024/06/19 daily CVS update output NetBSD source update
• 2024/06/19 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/19 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/18 daily CVS update output NetBSD source update
• 2024/06/18 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/18 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/17 daily CVS update output NetBSD source update
• 2024/06/17 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/17 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/17 Re: Automated report: NetBSD-current/i386 build failure Chavdar Ivanov
• 2024/06/17 re: race condition in kerberos? matthew green
• 2024/06/17 re: Automated report: NetBSD-current/i386 build failure matthew green
• 2024/06/17 Re: Automated report: NetBSD-current/i386 build failure Chavdar Ivanov
• 2024/06/16 daily CVS update output NetBSD source update
• 2024/06/16 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/06/16 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/16 re: Automated report: NetBSD-current/i386 build failure matthew green
• 2024/06/16 re: Automated report: NetBSD-current/i386 build failure matthew green
• 2024/06/16 re: Automated report: NetBSD-current/i386 build failure matthew green
• 2024/06/15 daily CVS update output NetBSD source update
• 2024/06/15 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/15 re: HEADS UP: plan to switch many ports over to GCC 12 soon matthew green
• 2024/06/15 re: race condition in kerberos? matthew green
• 2024/06/15 race condition in kerberos? Thomas Klausner
• 2024/06/15 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/15 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/14 daily CVS update output NetBSD source update
• 2024/06/14 Re: HEADS UP: plan to switch many ports over to GCC 12 soon Ryo ONODERA
• 2024/06/13 daily CVS update output NetBSD source update
• 2024/06/12 daily CVS update output NetBSD source update
• 2024/06/12 Re: shutdown/reboot taking a long time Frank Kardel
• 2024/06/11 daily CVS update output NetBSD source update
• 2024/06/11 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/11 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/11 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/11 Re: Automated report: NetBSD-current/i386 build failure Thomas Klausner
• 2024/06/11 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/10 Re: shutdown/reboot taking a long time Thomas Klausner
• 2024/06/10 Re: shutdown/reboot taking a long time T K Spindler (moof)
• 2024/06/10 daily CVS update output NetBSD source update
• 2024/06/10 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/10 Re: shutdown/reboot taking a long time Chavdar Ivanov
• 2024/06/10 Re: shutdown/reboot taking a long time Rhialto
• 2024/06/09 re: HEADS UP: plan to switch many ports over to GCC 12 soon matthew green
• 2024/06/09 Re: HEADS UP: plan to switch many ports over to GCC 12 soon Jan-Benedict Glaw
• 2024/06/09 shutdown/reboot taking a long time Thomas Klausner
• 2024/06/09 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/06/09 HEADS UP: plan to switch many ports over to GCC 12 soon matthew green
• 2024/06/08 daily CVS update output NetBSD source update
• 2024/06/07 daily CVS update output NetBSD source update
• 2024/06/06 daily CVS update output NetBSD source update
• 2024/06/05 daily CVS update output NetBSD source update
• 2024/06/05 Re: Specify swap device priority in fstab? Valery Ushakov
• 2024/06/05 Re: Specify swap device priority in fstab? Brad Spencer
• 2024/06/05 Re: Specify swap device priority in fstab? Valery Ushakov
• 2024/06/05 Re: Specify swap device priority in fstab? Paul Goyette
• 2024/06/05 Re: Specify swap device priority in fstab? Brad Spencer
• 2024/06/05 Specify swap device priority in fstab? Paul Goyette
• 2024/06/04 daily CVS update output NetBSD source update
• 2024/06/03 daily CVS update output NetBSD source update
• 2024/06/02 daily CVS update output NetBSD source update
• 2024/06/01 daily CVS update output NetBSD source update
• 2024/06/01 Re: Minor sysupgrade issue David Brownlee
• 2024/06/01 Re: Minor sysupgrade issue Brad Spencer
• 2024/06/01 Re: Minor sysupgrade issue Chavdar Ivanov
• 2024/06/01 Re: Minor sysupgrade issue Martin Husemann
• 2024/06/01 Minor sysupgrade issue Chavdar Ivanov
• 2024/06/01 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/06/01 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/31 daily CVS update output NetBSD source update
• 2024/05/31 Re: Curious new panic Chavdar Ivanov
• 2024/05/30 daily CVS update output NetBSD source update
• 2024/05/30 Re: Curious new panic maya
• 2024/05/30 Re: Curious new panic maya
• 2024/05/30 Re: Curious new panic Chavdar Ivanov
• 2024/05/30 Re: Curious new panic Markus Kilbinger
• 2024/05/30 Re: Curious new panic Jason Thorpe
• 2024/05/30 Re: Curious new panic Jason Thorpe
• 2024/05/30 Curious new panic Chavdar Ivanov
• 2024/05/29 daily CVS update output NetBSD source update
• 2024/05/29 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/29 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/28 daily CVS update output NetBSD source update
• 2024/05/28 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/27 daily CVS update output NetBSD source update
• 2024/05/26 daily CVS update output NetBSD source update
• 2024/05/25 daily CVS update output NetBSD source update
• 2024/05/25 Re: Does anyone use checknr(1)? nia
• 2024/05/24 daily CVS update output NetBSD source update
• 2024/05/24 Users of indent(1) (was: Re: Does anyone use checknr(1)?) Roland Illig
• 2024/05/24 Re: Does anyone use checknr(1)? B Harder
• 2024/05/24 Does anyone use checknr(1)? Roland Illig
• 2024/05/24 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/24 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/23 daily CVS update output NetBSD source update
• 2024/05/22 daily CVS update output NetBSD source update
• 2024/05/21 daily CVS update output NetBSD source update
• 2024/05/20 daily CVS update output NetBSD source update
• 2024/05/20 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/20 Build error Paul Goyette
• 2024/05/19 daily CVS update output NetBSD source update
• 2024/05/19 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/19 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/19 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/19 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/18 daily CVS update output NetBSD source update
• 2024/05/17 daily CVS update output NetBSD source update
• 2024/05/16 daily CVS update output NetBSD source update
• 2024/05/15 daily CVS update output NetBSD source update
• 2024/05/14 daily CVS update output NetBSD source update
• 2024/05/14 re: amdgpu laptops with 10 & current? matthew green
• 2024/05/14 Re: amdgpu laptops with 10 & current? Martin Husemann
• 2024/05/14 Re: amdgpu laptops with 10 & current? Vitaly Shevtsov
• 2024/05/14 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/14 Re: amdgpu laptops with 10 & current? Vitaly Shevtsov
• 2024/05/14 Re: amdgpu laptops with 10 & current? nia
• 2024/05/14 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/14 Re: aarch64-current build failure Chavdar Ivanov
• 2024/05/14 lldb 18.1.5 build failure under aarch64-current Chavdar Ivanov
• 2024/05/14 Re: amdgpu laptops with 10 & current? Patrick Welche
• 2024/05/14 Re: amdgpu laptops with 10 & current? Robert Swindells
• 2024/05/14 Re: amdgpu laptops with 10 & current? David Brownlee
• 2024/05/14 amdgpu laptops with 10 & current? nia
• 2024/05/13 daily CVS update output NetBSD source update
• 2024/05/12 daily CVS update output NetBSD source update
• 2024/05/12 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/12 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/12 aarch64-current build failure Chavdar Ivanov
• 2024/05/11 daily CVS update output NetBSD source update
• 2024/05/10 daily CVS update output NetBSD source update
• 2024/05/09 daily CVS update output NetBSD source update
• 2024/05/09 Re: modesetting vs intel in 10.0 Rhialto
• 2024/05/08 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/08 daily CVS update output NetBSD source update
• 2024/05/08 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/05/07 daily CVS update output NetBSD source update
• 2024/05/06 daily CVS update output NetBSD source update
• 2024/05/05 daily CVS update output NetBSD source update
• 2024/05/05 Re: continuous ffs_blkfree_common panic Andrius V
• 2024/05/04 daily CVS update output NetBSD source update
• 2024/05/04 Re: continuous ffs_blkfree_common panic Chuck Silvers
• 2024/05/04 Re: continuous ffs_blkfree_common panic Michael van Elst
• 2024/05/04 Re: continuous ffs_blkfree_common panic Martin Husemann
• 2024/05/03 daily CVS update output NetBSD source update
• 2024/05/03 Re: continuous ffs_blkfree_common panic Andrius V
• 2024/05/03 continuous ffs_blkfree_common panic Andrius V
• 2024/05/03 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/02 daily CVS update output NetBSD source update
• 2024/05/02 Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 2024/05/01 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/05/01 daily CVS update output NetBSD source update
• 2024/05/01 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/04/30 daily CVS update output NetBSD source update
• 2024/04/29 daily CVS update output NetBSD source update
• 2024/04/28 daily CVS update output NetBSD source update
• 2024/04/28 Thinkpad battery status Robert Swindells
• 2024/04/28 Re: Re: ThinkPad battery charge control Malte Dehling
• 2024/04/28 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/04/27 daily CVS update output NetBSD source update
• 2024/04/27 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/04/27 Re: ThinkPad battery charge control Dave Tyson
• 2024/04/26 daily CVS update output NetBSD source update
• 2024/04/26 amdgpu module hangs Reinoud Zandijk
• 2024/04/26 Re: new "compat" sets have really made sets harder to manage. Christos Zoulas
• 2024/04/25 Re: new "compat" sets have really made sets harder to manage. Martin Husemann
• 2024/04/25 daily CVS update output NetBSD source update
• 2024/04/25 ThinkPad battery charge control Malte Dehling
• 2024/04/25 Re: new "compat" sets have really made sets harder to manage. Christos Zoulas
• 2024/04/25 Re: new "compat" sets have really made sets harder to manage. Robert Swindells
• 2024/04/25 Re: new "compat" sets have really made sets harder to manage. nia
• 2024/04/25 Re: kern/58195: vmt(4) driver conflicts with open-vm-tools (Was: vmt driver) PHO
• 2024/04/24 daily CVS update output NetBSD source update
• 2024/04/24 Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• 2024/04/24 Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
• 2024/04/23 daily CVS update output NetBSD source update

• Earlier messages
• Later messages