From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.devel Subject: Re: plan for code freeze Date: Thu, 29 Aug 2002 16:15:09 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <200208292015.g7TKFAI13686@rum.cs.yale.edu> References: <200207181644.g6IGiuv11955@rum.cs.yale.edu> <200207191653.g6JGrpV26904@aztec.santafe.edu> <200208131634.g7DGYxf14020@rum.cs.yale.edu> <200208140515.g7E5F8R07436@wijiji.santafe.edu> <200208141439.g7EEd8o18274@rum.cs.yale.edu> <200208172008.g7HK8iu08874@wijiji.santafe.edu> <86u1llwrag.fsf@asgard.bp.aventail.com> <200208250526.g7P5QTS11987@wijiji.santafe.edu> <86hehfyoh6.fsf@asgard.bp.aventail.com> <200208291753.g7THrss11621@rum.cs.yale.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1030652223 19672 127.0.0.1 (29 Aug 2002 20:17:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 29 Aug 2002 20:17:03 +0000 (UTC) Cc: "Stefan Monnier" , emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17kVip-00056p-00 for ; Thu, 29 Aug 2002 22:16:55 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17kWFG-00068f-00 for ; Thu, 29 Aug 2002 22:50:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17kVk9-0001mY-00; Thu, 29 Aug 2002 16:18:17 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17kVhC-0001e1-00 for emacs-devel@gnu.org; Thu, 29 Aug 2002 16:15:14 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17kVh9-0001de-00 for emacs-devel@gnu.org; Thu, 29 Aug 2002 16:15:13 -0400 Original-Received: from rum.cs.yale.edu ([128.36.229.169]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17kVh9-0001dM-00; Thu, 29 Aug 2002 16:15:11 -0400 Original-Received: (from monnier@localhost) by rum.cs.yale.edu (8.11.6/8.11.6) id g7TKFAI13686; Thu, 29 Aug 2002 16:15:10 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 Original-To: Sam Steingold Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:7127 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:7127 > > CVS has special support for symlinks-in-the-repository, so it should > > work, and if it doesn't, then CVS will tell you (I seem to remember that > > there are limits to what CVS handles). > > It is already used for emacs/src/regex.[ch] which is symlinked > > with gnulib/regex.[ch]. > > this is a stunning revelation to me (I had some quite disastrous > experience with symlinks in the CVS some years ago, and the CVS manual > on the cvshome.org appears to support my understanding that symlink and > CVS do not work together at all). > > Could you please be more specific: how do symlinks work? I think you confuse the issue of revision-control of symlinks in your project, against using symlinks inside the repository. You indeed cannot store and revision control symlinks into the repository (the typical workaround is to use a revision-controlled Makefile which creates the symlinks and to just do `make' after every `cvs update'). But you can use symlinks inside the repository for purposes of providing the same RCS file(s) under a few different names in the CVS repository and such that updating one automatically updates the other(s) (because they really are one and the same). Stefan