X-Spam-Check-By: sourceware.org
Message-ID: <4638A730.244D362F@dessent.net>
Date: Wed, 02 May 2007 07:58:56 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Successfull Build of gcc on Cygwin WinXp SP2
References: <Pine DOT OSF DOT 4 DOT 21 DOT 0705012352360 DOT 16067-100000 AT ax0rm1 DOT roma1 DOT infn DOT it> <03e601c78bda$a0ed0dd0$0200a8c0 AT AMD2500> <4637C3B7 DOT 86D4E131 AT dessent DOT net> <053601c78c9c$2e59c390$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Dave Korn wrote:

> > that are shared across gcc/binutils/gdb/sim/etc.  If you later do "cvs
> > up" from the toplevel you'll accidently get the entire "src" tree
> 
>   No, you won't, unless you deliberately add the '-d' option.

Well sure, but then when someone checks in a change that involves
renaming or adding a subdirectory somewhere, your tree is silently
broken without any warning or indication, and you have to track it
down.  This can be a lot of head scratching and cursing until you figure
out that cvs was too dumb to add the directory to your repository.

I prefer to always use cvs up -dP outside of toplevel, which I update
with cvs up -lP.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/