current-users  

Messages by Thread

• • Re: Automated report: NetBSD-current/i386 build failure Robert Elz
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 build failure Robert Elz
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 build failure Thomas Klausner
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 build failure Hisashi T Fujinaka
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 build failure Rin Okuyama
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 build success NetBSD Test Fixture
• Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Bartek Krawczyk
  • Re: Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Michael van Elst
  • Re: Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Bartek Krawczyk
  • Re: Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Michael van Elst
  • Re: Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Bartek Krawczyk
  • Re: Raspberry Pi 3 aarch64 -current fails to find root fs label and boot. Michael van Elst
• How to recover a root partition with damaged boot blocks Thomas Mueller
  • re: How to recover a root partition with damaged boot blocks matthew green
  • Re: How to recover a root partition with damaged boot blocks Lloyd Parkes
  • Re: How to recover a root partition with damaged boot blocks Thomas Mueller
• LLONG_MAX not available from c++ Thomas Klausner
  • Re: LLONG_MAX not available from c++ Martin Husemann
  • Re: LLONG_MAX not available from c++ Thomas Klausner
  • Re: LLONG_MAX not available from c++ Joerg Sonnenberger
  • Re: LLONG_MAX not available from c++ Thomas Klausner
  • Re: LLONG_MAX not available from c++ Michael van Elst
  • Re: LLONG_MAX not available from c++ Martin Husemann
  • Re: LLONG_MAX not available from c++ RVP
  • Re: LLONG_MAX not available from c++ Valery Ushakov
  • Re: LLONG_MAX not available from c++ RVP
  • Re: LLONG_MAX not available from c++ Michael van Elst
  • Re: LLONG_MAX not available from c++ Martin Husemann
• clang-built NetBSD and rust Havard Eidnes
  • Re: clang-built NetBSD and rust Tobias Nygren
  • Re: clang-built NetBSD and rust Greg Troxel
• error installing libiconv-1.17 Riccardo Mottola
  • Re: error installing libiconv-1.17 Thomas Klausner
  • Re: error installing libiconv-1.17 Riccardo Mottola
  • Re: error installing libiconv-1.17 Greg Troxel
  • Re: error installing libiconv-1.17 Tobias Nygren
• Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 test failure Robert Elz
  • Re: Automated report: NetBSD-current/i386 test failure Christos Zoulas
  • Re: Automated report: NetBSD-current/i386 test failure Robert Elz
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Re: Automated report: NetBSD-current/i386 test failure Andreas Gustafsson
  • Re: Automated report: NetBSD-current/i386 test failure Martin Husemann
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
  • Automated report: NetBSD-current/i386 test failure NetBSD Test Fixture
• 10.0_BETA intelfb/drm on x220 thinkpad Staffan Thomen
  • Re: 10.0_BETA intelfb/drm on x220 thinkpad RVP
  • Re: 10.0_BETA intelfb/drm on x220 thinkpad Staffan Thomen
• CARP misbehaving on RPi2+ / RPI3 Greywolf
  • Re: CARP misbehaving on RPi2+ / RPI3 Michael van Elst
  • Re: CARP misbehaving on RPi2+ / RPI3 Greywolf
• IntelliJ IDEA for java development on NetBSD David Brownlee
  • Re: IntelliJ IDEA for java development on NetBSD Ron Georgia
  • Re: IntelliJ IDEA for java development on NetBSD David Brownlee
  • Re: IntelliJ IDEA for java development on NetBSD Ron Georgia
  • Re: IntelliJ IDEA for java development on NetBSD David Brownlee
  • Re: IntelliJ IDEA for java development on NetBSD David Brownlee
• Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Shoichi Yamaguchi
  • Re: Panic on today's -current aarch64 on Qemu (Oracle OCI VM) Chavdar Ivanov
• Panic on dump over fss César Catrián C .
  • Re: Panic on dump over fss J. Hannken-Illjes
  • Re: Panic on dump over fss César Catrián C .
  • Re: Panic on dump over fss J. Hannken-Illjes
  • Re: Panic on dump over fss César Catrián C .
• Re: nouveau: console stops updating Thomas Klausner
• Re: ipmi0: incorrect critical max Stephen Borrill
  • Re: ipmi0: incorrect critical max Lloyd Parkes
• Install /boot/boot.cfg for arm7 EFI ports Brook Milligan
• daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update
  • daily CVS update output NetBSD source update

• Earlier messages
• Later messages