[Fwd: Re: Less Checkout]

From: Robert Graf-Waczenski <rgw_at_lsoft.com>
Date: Mon, 31 Mar 2008 10:32:09 +0200

Sorry, fell into the "reply all" trap.

Robert

-------- Original Message --------

Subject:	Re: Less Checkout
Date:	Mon, 31 Mar 2008 10:29:54 +0200
From:	Robert Graf-Waczenski <rgw@lsoft.com>
To:	Ryan Schmidt <subversion-2008a@ryandesign.com>
References:	<db8aa2e80803301940s7d887e2bu8674cfa010c750c9@mail.gmail.com> <D882B70C-7463-4DF0-9F76-39B3CD3D51E9@ryandesign.com>

Ryan Schmidt wrote:
>
> On Mar 30, 2008, at 21:40, Alejandro Lopez Rama(correos) wrote:
>
>> I'm testing SVN to see if it fit our version control needs. One doubt 
>> i have is that each developer needs to have all the files of the 
>> project checked out in order to work.
>> It is correct? What we want is to check out only the sources to 
>> modify, and have a directory available with the last version of each 
>> source. This is especially important for compiling reasons, because 
>> we need to have the legal version of each include during the 
>> compilation process (when we saw SourceSafe, it had an option called 
>> "Shadow Folders", which leaves a copy of each file checked-in)
>>
>> It is possible to work in that way with SVN?
>
> I'm not sure I understand the question, and I haven't used SourceSafe 
> or any other revision control system other than Subversion, but 
> perhaps I should clarify that in Subversion, "check out" does not mean 
> "check out, so that nobody else can it check out"; rather, it means 
> "get a copy, and anybody else can also get a copy at the same time." 
> As you say, each developer should "check out" a working copy (that is 
> "get a copy") of the project they're working on. They modify files and 
> commit changes as they need to. Developers use "svn update" often to 
> retrieve others' changes. Does that answer your concern? Have you 
> already read the book available for free online at http://svnbook.org/ ?
>

Subversion 1.5 sparse checkouts are similar to SourceSafe's shadow 
folders. Pre-1.5 subversion, however, has nothing like this and requires 
that the developers check out isolated working copy folders for smaller 
repository sub-areas. With sparse checkouts, you can simply tell the 
client to checkout a higher level parent folder and leave out unwanted 
subfolders, which is probably what the OP wanted.

Robert

--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on 2008-03-31 10:37:00 CEST