From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: deleting rcs keywords from emacs sources Date: 26 Mar 2004 19:46:56 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <4242667.1080067569994.JavaMail.root@tintin.london.ongenie.net> <20040323214737.GA21737@fencepost> <1080200708.749.486.camel@localhost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1080327086 20013 80.91.224.253 (26 Mar 2004 18:51:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 26 Mar 2004 18:51:26 +0000 (UTC) Cc: miles@gnu.org, Andre Spiegel , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Mar 26 19:51:08 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 1B6wQ8-0003QX-00 for ; Fri, 26 Mar 2004 19:51:08 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B6wQ7-0006X9-00 for ; Fri, 26 Mar 2004 19:51:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B6wNF-00031q-8T for emacs-devel@quimby.gnus.org; Fri, 26 Mar 2004 13:48:09 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B6wMw-0002hD-95 for emacs-devel@gnu.org; Fri, 26 Mar 2004 13:47:50 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B6wMJ-0001mO-8h for emacs-devel@gnu.org; Fri, 26 Mar 2004 13:47:43 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B6wMH-0001kw-Ll for emacs-devel@gnu.org; Fri, 26 Mar 2004 13:47:09 -0500 Original-Received: from fencepost.gnu.org ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.24) id 1B6wHL-0007i7-5W; Fri, 26 Mar 2004 13:42:03 -0500 Original-To: rms@gnu.org In-Reply-To: Original-Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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:20971 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20971 Richard Stallman writes: > The user doesn't have CVS access, my fix is not readily > backported into the version of the file he has, so I send him > the entire current source file. Later, that person has another > problem, and reports it along with the version number of the > file I sent him. Without version numbers in the files, this is > very difficult, if not impossible to keep track of. > > I can follow how this is useful for you. I would guess that only a > few Lisp file maintainers do this, though. FWIW, AUCTeX uses RCS tags to announce the version number used (either released version or CVS revision and build date) in bug reports sent by the standard bug reporting commands. Since we don't release that often, this information helps quite a lot in tracking what code base the bug report refers to. > If you put a date manually into the files when you send an entire > file to someone, it would achieve the same purpose, right? You'd be > doing it manually instead of automatically. If somebody checks out and compiles my CVS archive, I won't be in the position of putting dates into his files manually. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum