From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Andre Spiegel Newsgroups: gmane.emacs.devel Subject: Re: RCS keyword removal Date: Mon, 12 Apr 2004 11:14:56 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <1081761295.770.151.camel@localhost> References: <20040410060006.GA24729@fencepost> <1081696710.770.115.camel@localhost> <20040411155130.GA30439@fencepost> <1081703812.770.131.camel@localhost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1081761754 23927 80.91.224.253 (12 Apr 2004 09:22:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Apr 2004 09:22:34 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Apr 12 11:22:27 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BCxe6-00031W-00 for ; Mon, 12 Apr 2004 11:22:26 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BCxe6-00057G-00 for ; Mon, 12 Apr 2004 11:22:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BCwbI-0007Ih-DB for emacs-devel@quimby.gnus.org; Mon, 12 Apr 2004 04:15:28 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BCwar-0007Gv-AS for emacs-devel@gnu.org; Mon, 12 Apr 2004 04:15:01 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BCwap-0007Fe-DT for emacs-devel@gnu.org; Mon, 12 Apr 2004 04:15:00 -0400 Original-Received: from [193.113.160.14] (helo=mail.o2.co.uk) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BCwal-0007DG-A7; Mon, 12 Apr 2004 04:14:55 -0400 Original-Received: from [217.231.188.253] (217.231.188.253) by mail.o2.co.uk (7.0.020) (authenticated as andre.spiegel@o2online.de) id 406D36E900312377; Mon, 12 Apr 2004 10:14:01 +0100 Original-To: Miles Bader In-Reply-To: X-Mailer: Ximian Evolution 1.4.5 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21519 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21519 On Mon, 2004-04-12 at 03:48, Miles Bader wrote: > I'd like to do this, but have been nervous to because of my uncertainity > about CVS's behavior. If people think it's safe to use `-kb' globally > I'll do that I'm not sure I understand the scope you are talking about. If you mean to switch off keyword expansion in the Emacs CVS repository as a whole (so that I would be pretty much the only one who enables it locally), then we might as well get rid of those keywords in vc-*.el altogether, because it's really no point if only I keep them. It was my understanding that these changes would only apply to the version of Emacs that is managed in parallel using Arch. My impression was further that the Arch stuff is more of an experimental setup, and not the main place of any development. You also said that Arch has better features to identify the version of the entire system, than CVS with its keywords which apply only to single files. Based on this, I would argue that the RCS keywords ought to be enabled in the CVS repository (and thus be enabled in every developer's work area by default, and the released versions of Emacs), until perhaps one day Arch is used to maintain the Emacs sources completely (and releases are made from the Arch tree). > If I'm interpreting the docs correctly, BTW, switching to `-kb' will > leave expanded keywords in currently checked-out files unchanged (that > is, if CVS stores keywords unexpanded in the repository, adding `-kb' > _won't_ suddently cause keywords in checked out files to revert to their > unexpanded forms), which might be slightly confusing for anyone relying > on RCS keywords in bug reports. I don't quite see the point here. Why don't you just check out your work area anew, and all your keywords will be unexpanded? All of this assumes that we are only talking about disabling the keywords locally (i.e. using "cvs update -kb file", rather than "cvs admin -kb file").