From owner-freebsd-current  Wed Dec 29 10:40:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id 79075156E6; Wed, 29 Dec 1999 10:40:45 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA28360;
	Wed, 29 Dec 1999 10:40:47 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: Peter Wemm <peter@netplex.com.au>,
	Bill Fumerola <billf@chc-chimes.com>, obrien@FreeBSD.org,
	Donn Miller <dmmiller@cvzoom.net>, current@FreeBSD.org
Subject: Re: gcc compile error 
In-reply-to: Your message of "Tue, 28 Dec 1999 23:01:43 PST."
             <199912290701.XAA37455@rah.star-gate.com> 
Date: Wed, 29 Dec 1999 10:40:47 -0800
Message-ID: <28357.946492847@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> XFree86 3.9.xxx  was cvsup on December 24th   I am sorry but this is 
> sufficient information to reproduce the problem.

Not if you actually want the problem solved.  There's this thing
called "making it easy on the people you're demanding things of" in
order that they might have some chance of actually doing it.
Insisting that someone cvsup the entire X source tree, as you've
clearly *already* done, hardly falls into the category of attempting
to save the gcc maintainers work in attempting to track down the
problem you're complaining about.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message