From owner-freebsd-current  Tue Feb  6 16:29:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA28226
          for current-outgoing; Tue, 6 Feb 1996 16:29:01 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28206
          Tue, 6 Feb 1996 16:28:57 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03938; Tue, 6 Feb 1996 17:26:27 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199602070026.RAA03938@phaeton.artisoft.com>
Subject: Re: FS PATCHES: THE NEXT GENERATION
To: julian@ref.tfs.com (Julian Elischer)
Date: Tue, 6 Feb 1996 17:26:27 -0700 (MST)
Cc: terry@lambert.org, current@FreeBSD.ORG, hackers@FreeBSD.ORG
In-Reply-To: <199602062321.PAA01295@ref.tfs.com> from "Julian Elischer" at Feb 6, 96 03:21:38 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

> Ah yes but:
> now that you have a sup+cvs setup, you can keep your diff sets up-to date
> relatively easily, and if you send them as diffs
> then there is a good chance that even if there is a time-lag induced
> collision, it will be caught and fixed, 
> also many files get changes that are automatically resolved..

I have uploaded a FS_PATCHED.diff.gz to incoming on freefall.

This was generated with "cvs diff -c" in /sys.

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).

> as long as you don't check in your changes in your cvs tree, it's much
> more resistant to spamming, to do it this way..

I don't check in my changes to my CVS tree.

> > I can provide the changes as diffs if you need them that way; I'll warn
> > you that you'll be in exactly the same boat applying them as the original
> > diff sets I sent (that's why I went to the trouble of sup + cvs + ...).
> 
> err why?

See above.  "cvs diff -c" does not result in a file that can be used as
input to "patch" without some post-processing.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.