From owner-freebsd-stable Fri Jun 15 22: 8:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-172.zoominternet.net [24.154.28.172]) by hub.freebsd.org (Postfix) with ESMTP id EFE2437B407 for ; Fri, 15 Jun 2001 22:08:07 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.4/8.11.4) with ESMTP id f5G58v888295 for ; Sat, 16 Jun 2001 01:08:57 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sat, 16 Jun 2001 01:08:57 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: XFree86-4.1.0_4 still broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 14 Jun 2001, Kenneth Mays wrote: > What I am asking for probably already exists but it was more to state that > when you get a certain application to successfully install on a release or > STABLE platform if it could be documented somewhere. > > Most of the time we install applications or hardware but don't always list > how we fixed an issue when we got something to work that didn't work > normally or install software that hit a quirk or two. Isn't that what send-pr is for? Include your patch in the PR and CC the maintainer. In the case of hardware, that's perhaps a different story, but you could file a PR with a documentation change, so that it would make it into either the FAQ or the handbook. At least that way, it would be trackable, and although it might take some time before your change gets incorporated, it's less likely to be lost outright. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message