From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 17:34:31 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAC101065675 for ; Fri, 6 Jun 2008 17:34:31 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id A769B8FC1D for ; Fri, 6 Jun 2008 17:34:31 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1516660rvf.43 for ; Fri, 06 Jun 2008 10:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=SEP3lgIYy3dS17yob9QM5SVdmFkzU2kd5Iwjxebzt0c=; b=t8WlmVjpD0DE7gr6/1nT83pTHO6PVYQjYBKwzwcNi2H0p8roLW8EcLS1YKxA+oNUsK T1UJX9O/4DgKVuWaTijH6LkhzKs8Jtis2vVbE7Po5kZQj6Y9yaZpjh+4hkmrgRkKB7gk 5lM39bf7uDE2B5f6az0fqBQipd9I941LbsHTk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=RWQ4p3jpHX2A3MpnnwKhLsU3F7ZvvyYSSaxgAbVpJTaXpLgXNRm3hOsdNVn0AWTU3t rxy5U3QzGhk4YbEn6Ek4kGroyJSNRK/HvrVrfT3zC00dnn7ey4PoPUgnmuyG7xd0DXot gL+2YzJ9qedHTvLr0itLejevBUW1ql1pQ3Zok= Received: by 10.141.153.17 with SMTP id f17mr226477rvo.267.1212773671407; Fri, 06 Jun 2008 10:34:31 -0700 (PDT) Received: from dhcp-128-107-159-165.cisco.com ( [128.107.159.165]) by mx.google.com with ESMTPS id f21sm7823358rvb.0.2008.06.06.10.34.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 06 Jun 2008 10:34:30 -0700 (PDT) Message-Id: From: Garrett Cooper To: "Peter Wemm" In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Fri, 6 Jun 2008 10:36:05 -0700 References: <20080606155541.GA90949@hub.freebsd.org> X-Mailer: Apple Mail (2.924) Cc: Ian FREISLICH , current@freebsd.org Subject: Re: Anyone else seeing this (cvs wierdness)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2008 17:34:31 -0000 On Jun 6, 2008, at 10:24 AM, Peter Wemm wrote: > On Fri, Jun 6, 2008 at 8:55 AM, David O'Brien > wrote: >> On Fri, May 16, 2008 at 04:12:39PM +0200, Ian FREISLICH wrote: >>> Recently - I guess in the last month or two - successive cvs updates >>> always "updates" files in the following directories, this with no >>> update to the CVS repo: >>> >>> cddl/contrib/opensolaris >>> contrib/ntp >>> contrib/ipfilter >>> contrib/expat >>> contrib/tcsh >>> >>> I sync a local CVS repo using cvsup and I update my source using >>> 'cvs -q update -PdA' >> >> Why are you always using "update -A"? Basically all the reports of >> weirdness are due to folks not fully understanding what -A does and >> is >> for. >> >> If -A removes stickly dates, tags, and (what you're seeing here) >> stickly >> options. Options can be set locally, in the ,v file on the >> server. Some >> keywords (such as $Name$) may need to be updated due to "update -A". > > We use -A because we've often messed with sticky dates and tags in our > checked out copy and want to reset anything we've forgotten and start > from a known state. For the last 14 years, -A has done exactly that. > If a stray sticky date or sticky tag had been set, -A would reset the > tag and fetch a new copy and life was good. > > This is not what is happening now. If the server has a nonstandard > rcs keyword expansion mode, cvs fetches a fresh copy, each and every > time. Even if the checked out copy has the correct expansion mode. > Over and over and over again. > > Many places in the source tree were affected by clowns using 'cvs > import -ko' in spite of it being removed from the instructions in 1997 > and no longer being part of standard procedure. Ports is badly > affected by -ko at this point. +1 for that. Besides, not using -A can prove to be problematic as Kris pointed out to me when doing development and stuff isn't 100% synced between my local copy and HEAD. -Garrett