[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Less Checkout

From: Ryan Schmidt <subversion-2008a_at_ryandesign.com>
Date: Sun, 30 Mar 2008 23:05:06 -0500

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/ ?

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-31 06:06:05 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.