svn-checkout

While trying to checkout code from a repository online I got the following Error E175002: REPORT of '/repos/xxx/!svn/vcc/default' I am trying to checkout the code from a remote computer After long research, I finally found a solution the solution was to put allow from all in the svn configuration on httpd.conf : <Directory /repos> ... allow from all ... </Directory> The svn checkout is working fine now The above are for apache 2.2 if you use apache 2.4 <Directory /repos> ... require all granted ... </Directory> In my case I had E175002 because of missing DNS records of Subversion server. I had

I have an SVN project with tree like this: /project /dir1 /subdir1 -file1 -file2 ..... -file1 -file2 ..... /dir2 -file1 -file2 ..... /dir3 /subdir1 -file1 -file2 ..... /subdir2 -file1 -file2 ..... /subdir3 -file1 -file2 ..... /subdir4 -file1 -file2 ..... /dir4 -file1 -file2 ..... -file1 -file2 I need to checkout all files from /project full /dir1 full /dir2 full /dir4 From /dir3 I need only /subdir1 and /subdir3 Can I checkout these files/folders using svn commandline with some kind of depth? If so how can I do it? Can I add subdir2 to dir3 after a checkout? How can I update working copy

I'm using TortoiseSVN and I want to do a Checkout of an existing repository into a local directory. However, I only want to pull down certain portions of the file tree. Is there a way I can do that? For instance: /trunk /project-A /project-B /project-C Let's say I just want to pull down trunk, project-A and project-B. How do I do that? It looks like you were successful but I wanted to include a step-by-step guide in the hopes that it is helpful to others. Checkout trunk into a working copy with depth = "Only this item" Open working copy Go to repo browser from the working copy Select your

What is the exact difference between SVN checkout and SVN export? From what I know, export does not include the .svn directory which include metadata, and checkout included that .svn directory. Yet, my colleague had this problem recently that there is a different behaviour for the stuff compiled from sources that is checkout and exported from SVN repo. Both of them compiled correctly, but the one compiled from svn export works, but the one that is checked out doesn't work at all. PS: The stuff being compiled is the Linux 2.4 kernel that is being used in an embedded device. The image compiles

Is it possible to execute build.xml script with Maven? This script checksout all my projects and subprojects and I've just got used to using maven, didn't really use much of an ant before and I know ant can be used with Maven. So my question is: how? I'm really not a big fan of this approach (either use Ant, or Maven, but not a bastard mix) but you can use an external build.xml with the Maven AntRun Plugin : <project> ... <build> <plugins> ... <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> <configuration> <tasks> <taskdef resource="net/sf

Is it possible to checkout only those files from a SVN repository that were modified in a revision or range of revisions, without checking out any files that were not modified? My suggestion is in the same lines as flolo suggests. But, takes a range. You could the following shell function. function checkout_files_in_revrange() { svn_url=$1; start_rev=$2; end_rev=$3; for theCheckoutCanditate in `svn log -r $start_rev:$end_rev --verbose --incremental | grep " M " | cut -f5 -d' ' | cut -f3- -d/` do svn co $svn_url/$theCheckoutCandidate -q; done } There is afaik now direct way to get just the

How can I list files CVS without an initial checkout? In subversion I can simply do "svn ls http://svn.svn.com " in CVS how can I do this? For example I've got this CVS connection: pserver:anonymous@evocms.cvs.sourceforge.net:/cvsroot/evocms How can I list all files in it? UPDATE: I'm doing this: c:\>set CVSROOT=pserver:anonymous@evocms.cvs.sourceforge.net:/cvsroot/evocms c:\>cvs -list ---> doesn't work, prints out the help screen If it's a one-off operation you don't need to set the CVSROOT environment variable. Just use the -d argument for ad-hoc repository specification. If your version of