From owner-freebsd-hackers  Tue Feb  6 17:59:11 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA03143
          for hackers-outgoing; Tue, 6 Feb 1996 17:59:11 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA03137
          Tue, 6 Feb 1996 17:59:09 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id RAA01737; Tue, 6 Feb 1996 17:59:07 -0800
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199602070159.RAA01737@ref.tfs.com>
Subject: Re: FS PATCHES: THE NEXT GENERATION
To: terry@lambert.org (Terry Lambert)
Date: Tue, 6 Feb 1996 17:59:06 -0800 (PST)
Cc: terry@lambert.org, current@FreeBSD.ORG, hackers@FreeBSD.ORG
In-Reply-To: <199602070026.RAA03938@phaeton.artisoft.com> from "Terry Lambert" at Feb 6, 96 05:26:27 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> The output doesn't look particularly useful as input to "patch", unless
> you write an awk/perl script to reformat the "cvs diff" file information
> (this seems to be more work than checking out a spamable tree).
> 
it always works for me...
Patch is very good about knowing which bits of the patch file are CVS guff,
and tends to ignore that..
I've done 150 file patches with a simple
"cvs diff -c sys"

> See above.  "cvs diff -c" does not result in a file that can be used as
> input to "patch" without some post-processing.
I bet you'd be surprised..