From owner-freebsd-current Wed Mar 13 03:31:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA24163 for current-outgoing; Wed, 13 Mar 1996 03:31:34 -0800 (PST) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA24156 for ; Wed, 13 Mar 1996 03:31:32 -0800 (PST) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.7.4/8.6.9) with ESMTP id DAA01053 for ; Wed, 13 Mar 1996 03:31:30 -0800 (PST) To: current@freebsd.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Wed, 13 Mar 1996 00:46:25 PST." <199603130846.AAA03007@precipice.shockwave.com> Date: Wed, 13 Mar 1996 03:31:29 -0800 Message-ID: <1047.826716689@pain.csrv.uidaho.edu> From: Faried Nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina wrote... No, it's actually better if the bug reports come to US first. The reason being that most vendors would say "pshaw, you guys are idiots." whereas there are a bunch of us on the mailing list who can point to the exact bits of trivia in RFC-793 and sample "killer packets" to get these guys to fix their TCP implementation. for xylogics/annex it's annex_support@xylogics.com i believe. any ideas on how i should compose my `bug report'? i've never really done this before. faried.