From owner-freebsd-current Sun Jan 26 02:18:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA00859 for current-outgoing; Sun, 26 Jan 1997 02:18:05 -0800 (PST) Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA00843 for ; Sun, 26 Jan 1997 02:18:00 -0800 (PST) Received: from plm.xs4all.nl (asd-isdn03-17.dial.xs4all.nl [194.109.46.82]) by magigimmix.xs4all.nl (8.7.6/XS4ALL) with ESMTP id LAA17155 for ; Sun, 26 Jan 1997 11:17:58 +0100 (MET) Received: (from plm@localhost) by plm.xs4all.nl (8.8.4/8.8.4) id LAA00391; Sun, 26 Jan 1997 11:16:39 +0100 (MET) To: freebsd-current@freebsd.org Subject: update to submitted bug report From: Peter Mutsaers Date: 26 Jan 1997 11:16:39 +0100 Message-ID: <87pvysn3lk.fsf@localhost.xs4all.nl> Lines: 13 X-Mailer: Gnus v5.2.39/Emacs 19.34 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I submitted bug report kern/2562 a week ago. Today I recompiled my kernel and the problem is gone. Somehow it seems to have been solved in the meantime, but on cvs-all I didn't see any activity related to my bugreport. How should I send a follow-up to a bugreport submitted through send-pr? -- Peter Mutsaers | Abcoude (Utrecht), | Trust is a good quality plm@xs4all.nl | the Netherlands | for other people to have