From owner-freebsd-hackers  Sat Jun 22 15:50:02 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA14435
          for hackers-outgoing; Sat, 22 Jun 1996 15:50:02 -0700 (PDT)
Received: from critter.tfs.com ([140.145.16.108])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14407;
          Sat, 22 Jun 1996 15:49:59 -0700 (PDT)
Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id PAA04956; Sat, 22 Jun 1996 15:49:26 -0700 (PDT)
To: Terry Lambert <terry@lambert.org>
cc: alk@Think.COM (Tony Kimball), hackers@freefall.freebsd.org
Subject: Re: cvs commit: src/etc/mtree BSD.usr.dist 
In-reply-to: Your message of "Sat, 22 Jun 1996 15:06:53 PDT."
             <199606222206.PAA22895@phaeton.artisoft.com> 
Date: Sat, 22 Jun 1996 15:49:25 -0700
Message-ID: <4954.835483765@critter.tfs.com>
From: Poul-Henning Kamp <phk@freebsd.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Terry, with all these strong ideas about How The World Should Be According
To Terry, I'm surprised that I still don't see patches from you.

Poul-Henning

PS:
Let me clarify what I mean by patch in this context, since past experience
have shown that you don't understand this concept:

A patch is a file that containes:
	1. Readable english explanation of what this patch does,
	   in sufficient detail that people can review the changes.
	   One patch will do one thing, Ie, don't mix several changes
	   into one patch file.

	2. Precise decription of the code version that is the reference
	   for this patch.

	3. Input suitable for the patch(1), such that when applied to
	   the code base described in 2, it will apply cleanly.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.