Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA04177; Mon, 25 Dec 95 23:41:16 EST
Received: from TERTIUS.MIT.EDU by MIT.EDU with SMTP
	id AA05460; Mon, 25 Dec 95 23:40:49 EST
Received: (from hartmans@localhost) by tertius.mit.edu (8.6.12/8.6.9) id XAA15953; Mon, 25 Dec 1995 23:40:58 -0500
Date: Mon, 25 Dec 1995 23:40:58 -0500
From: Sam Hartman <hartmans@MIT.EDU>
Message-Id: <199512260440.XAA15953@tertius.mit.edu>
To: krbdev@MIT.EDU
Subject: CVS is your friend; AFS gets backed up


	In other projects where I have used CVS, I have found it
useful to check in work in progress on a separate branch if it will be
taking a while to complete instead of just keeping it on local disk.
This has two distinct advantages:

* You back up your changes in progress; I have been known to have
horrible errors with delete-region and query-replace that it's nice to
back out, and hardware does fail, as well all know.

*  You can test your work on multiple platforms.

	I suggest that members of the Kerberos team might be well
served to become familiar enough with CVS branching that they can
effectively use it for similar strategies.  It won't solve all
data-loss problems, but it could help in the future.


--Sam

