From owner-freebsd-hackers Thu Feb 12 07:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13790 for hackers-outgoing; Thu, 12 Feb 1998 07:58:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA13776 for ; Thu, 12 Feb 1998 07:58:12 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA08392; Thu, 12 Feb 1998 07:58:11 -0800 Date: Thu, 12 Feb 1998 07:58:11 -0800 (PST) From: Brian Handy To: Steve Price Cc: hackers@FreeBSD.ORG Subject: Re: ftp://freebsd.org - RIP In-Reply-To: <34E2D7C6.59E2B600@hiwaay.net> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [Steve says about ports] >Yes, putting them in a PR is TRT, but they should be uuencoded >tarballs. All to many times I have had to spend extra time sorting >out snarf-and-barf errors. I would go so far as to say all but the >most trivial of patches should be done this way. I thought people were starting to lean towards shar archives for this sort of thing. I certainly dig shar archives, but if the people that actually have to do the work prefer otherwise, I'd like to know (as one of those folks who occasionally submit port stuff). I guess the same applies for patches...I didn't know that was even an issue. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe hackers" in the body of the message