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: Sun, 11 Apr 2004 19:16:52 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <1081703812.770.131.camel@localhost> References: <20040410060006.GA24729@fencepost> <1081696710.770.115.camel@localhost> <20040411155130.GA30439@fencepost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1081704446 11404 80.91.224.253 (11 Apr 2004 17:27:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 11 Apr 2004 17:27:26 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Apr 11 19:27:18 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 1BCijm-0000DZ-00 for ; Sun, 11 Apr 2004 19:27:18 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BCijl-00011a-00 for ; Sun, 11 Apr 2004 19:27:17 +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 1BCiiU-0007kA-Fj for emacs-devel@quimby.gnus.org; Sun, 11 Apr 2004 13:25:58 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BCii5-0007hO-9v for emacs-devel@gnu.org; Sun, 11 Apr 2004 13:25:33 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BCiaM-0004Xn-Kt for emacs-devel@gnu.org; Sun, 11 Apr 2004 13:18:05 -0400 Original-Received: from [193.113.160.15] (helo=mail.o2.co.uk) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BCiZi-0004GB-Mb; Sun, 11 Apr 2004 13:16:54 -0400 Original-Received: from [217.231.158.128] (217.231.158.128) by mail.o2.co.uk (7.0.020) (authenticated as andre.spiegel@o2online.de) id 406D3D6B002E4918; Sun, 11 Apr 2004 18:17:27 +0100 Original-To: Miles Bader In-Reply-To: <20040411155130.GA30439@fencepost> 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:21483 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21483 Miles wrote: > Ideally I could globally use the CVS -kb option on checkout/update to prevent > all keyword expansion, but the CVS docs are very unclear on the actual effect > of that, e.g what would the actual value of existing embedded keywords (in > existing code, or new code committed by people who _didn't_ globally force > -kb, i.e., most people)? Keywords are only expanded in the checked-out versions of files. The expanded form is never stored in the RCS master files. So, if somebody switches off keyword expansion locally for himself (in a single command, or permanently for an entire working directory), that doesn't affect anybody else using the repository. Switching off keyword expansion by default in the repository, as Andreas suggested, would defeat the purpose of those keywords altogether, though. The point is that in released versions of the files, the keywords ought to be expanded, otherwise they are useless, and I could just do as RMS suggested and stamp the files myself when I send them out. I doesn't really address the problem keywords are needed for, but I explained that already. When merges are done within CVS, keywords shouldn't be causing any trouble, because files are merged with keywords unexpanded, or at least there's an option to say it should be that way. However, when you use the files from CVS in another version control system (Arch, in your case), the issue becomes fuzzy. A general approach might be to switch off keyword expansion for anything that is checked in to Arch. Alternatively, a feature to tell Arch to ignore certain kinds of differences could be implemented.