Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.bugs.4bsd
Subject: Re: Chris Torek's control-T package
Message-ID: <6848@mimsy.UUCP>
Date: Fri, 29-May-87 23:25:35 EDT
Article-I.D.: mimsy.6848
Posted: Fri May 29 23:25:35 1987
Date-Received: Sun, 31-May-87 12:44:03 EDT
References: <1293@ubvax.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 20
Summary: Use a revision control system

In article <1293@ubvax.UUCP> vix@ubvax.UUCP (Paul Vixie) writes:
>... As much as I'd enjoy having a working control-T, I don't want to have to
>back out Chris' patch whenever I need to install a bsd-fixes patch -- 
>which I would have to do, some time down the road, when UCB patches a
>section of code that Chris' patch has altered.

We---by which I mean the University of MD CS Department---keep all
our kernel sources in RCS, so that we can retrieve Berkeley revisions
so as to see just what was changed, and properly merge any conflicting
changes.  This is time-consuming but not difficult.  (In other words,
it is a royal pain, but when ya just gotta have a feature. . . .)

No one at Berkeley really wants to uglify the tty driver yet more.
Someone will probably rewrite the whole thing sometime soon.  Maybe
(if someone can jar certain AT&T stigmata loose from SysV licencing,
or if someone reimplments them from existing descriptions) we can
use streams and do it right instead.  Ah well.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris