X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <03e601c78bda$a0ed0dd0$0200a8c0@AMD2500> <4637C3B7.86D4E131@dessent.net> <053601c78c9c$2e59c390$2e08a8c0@CAM.ARTIMI.COM> <4638A730.244D362F@dessent.net> Subject: RE: Successfull Build of gcc on Cygwin WinXp SP2 Date: Wed, 2 May 2007 19:13:21 +0100 Message-ID: <001001c78ce5$91299790$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4638A730.244D362F@dessent.net> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 02 May 2007 15:59, Brian Dessent wrote: > 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. If you examine the wording carefully, you can infer that doing "cvs up" from toplevel without the -d option does not preclude using -d at levels below that.... > 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. Hmmm, I can't think off the top of my head of anything much better than find . -maxdepth 1 -type d | grep -v '\.$' | grep -v CVS | xargs cvs -q -z9 up -dP > I prefer to always use cvs up -dP outside of toplevel, which I update > with cvs up -lP. I believe the -P option is probably superfluous in that second example! :) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/