From owner-freebsd-current  Mon Aug  3 17:26:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA04814
          for freebsd-current-outgoing; Mon, 3 Aug 1998 17:26:29 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA04809;
          Mon, 3 Aug 1998 17:26:27 -0700 (PDT)
          (envelope-from imp@village.org)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0z3Uvh-0006OW-00; Mon, 3 Aug 1998 18:26:17 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id SAA06411; Mon, 3 Aug 1998 18:16:35 -0600 (MDT)
Message-Id: <199808040016.SAA06411@harmony.village.org>
To: freebsd-ctm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: CTM checksum errors?
Date: Mon, 03 Aug 1998 18:16:35 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Greetings,
	am I the only one to get boatloads of CVS checksum errors when
trying to apply cvs-cur 4493 and later?  The number of such errors
leads me to believe that somebody "oopsed" and is now generating the
CTM diffs from a tree that is updated by cvsup with the new "ignore
whitespace" option turned on, which is FUBARing the checksums for the
CTM generation.

Other than CTM being an orphan right now, comments?

Warner

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message