From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28954 invoked by alias); 22 Mar 2007 15:51:57 -0000 Received: (qmail 28944 invoked by uid 22791); 22 Mar 2007 15:51:56 -0000 X-Spam-Check-By: sourceware.org Received: from lon-del-02.spheriq.net (HELO lon-del-02.spheriq.net) (195.46.50.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 Mar 2007 15:51:52 +0000 Received: from lon-out-02.spheriq.net ([195.46.50.130]) by lon-del-02.spheriq.net with ESMTP id l2MFq6AI031052 for ; Thu, 22 Mar 2007 15:52:06 GMT Received: from lon-cus-02.spheriq.net (lon-cus-02.spheriq.net [195.46.50.38]) by lon-out-02.spheriq.net with ESMTP id l2MFpmD5012353 for ; Thu, 22 Mar 2007 15:51:48 GMT Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by lon-cus-02.spheriq.net with ESMTP id l2MFpl4J030331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 22 Mar 2007 15:51:48 GMT Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id ECC5ADA42 for ; Thu, 22 Mar 2007 15:51:46 +0000 (GMT) Received: from mail1.bri.st.com (mail1.bri.st.com [164.129.8.218]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id AE3A647629 for ; Thu, 22 Mar 2007 15:51:46 +0000 (GMT) Received: from [164.129.15.13] (bri1043.bri.st.com [164.129.15.13]) by mail1.bri.st.com (MOS 3.7.5a-GA) with ESMTP id CIQ36337 (AUTH stubbsa); Thu, 22 Mar 2007 15:51:45 GMT Message-ID: <4602A611.6060907@st.com> Date: Thu, 22 Mar 2007 15:51:00 -0000 From: Andrew STUBBS User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: binutils@sourceware.org Subject: Re: SVN for src (was Re: Binutils 2.18 prep) References: <46025531.90105@st.com> <20070322150018.GA4566@caradoc.them.org> <20070322152751.GA5538@caradoc.them.org> In-Reply-To: <20070322152751.GA5538@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00309.txt.bz2 Daniel Jacobowitz wrote: > Check out the trunk using "svn co -N" for non-recursive. You will get > only the trunk - no subdirectories. Unlike in CVS they will never > spontaneously appear after this point; "svn up" will only create new > directories when it updates through a revision in the repository that > created the directory. Otherwise, it appears to assume that the > directory is deliberately missing if it is not mentioned in > .svn/entries. However, an explicit "svn up gdb" in this case will > work! Try a commit. I'm fairly sure that any subsequent check-outs within the working-copy are separate - you can't check-in changes to different directories simultaneously. It will be perfectly adequate for building and diffing, of course. > Not everything is rosy. "svn cp . $repo/branches/new-branch" will > copy the omitted directories, which is peculiar, so we would either > need people branching to get a hypothetical svn which didn't do that > or use a script to create branches. But it's much less messy than > using externals would be. What's wrong with creating a branch that contains everything? This is the natural way to work with svn - copies are not expensive. One can then check out modules on the branch in the same way as the trunk. This does raise an interesting point: it would not be trivial to 'svn switch' to different branches. Not impossible, but not trivial. Andrew