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

RE: checkout on existing directory structure

From: Stephen Butler <sbutler_at_elego.de>
Date: Fri, 29 May 2009 16:28:17 +0200

Quoting Roger Lipscombe <rogerl_at_1e.com>:

> > -----Original Message-----
> > From: kovlensky_at_interia.pl [mailto:kovlensky_at_interia.pl]
> > Sent: Fri 29 May 2009 14:36
> > To: users_at_subversion.tigris.org
> > Subject: checkout on existing directory structure
> >
> > Scenario - files/directories are added to svn by svn import.
> Further > updates require svn commit. To commit, svn must be
> checkouted first. > How to checkout imported structure on existing
> files/dirs structure?
> >
> > Example: svn holds a file, let's say a/b/c/d.txt. File >
> /x/a/b/c/d.txt exists on filesystem. As the file was just imported
> > to svn both disk and svn file match. What should I do to get >
> equivalent of svn checkout in /x directory having files/dirs >
> present, but unversioned, on filesystem? The final result I need are
> > all files/dirs in svn versioned (i.e. .svn dirs appers) and all
> > remaining files (i.e. unversioned) left intact.

> Check out somewhere else; write a script to remove everything but
> the .svn directories; copy those over the top of your original (thus
> turning it into a working copy); commit.

Better:

   cd /x
   svn checkout $url --force

This will preserve existing files. Note that a real obstruction
(e.g., an incoming file onto an existing directory) will still cause
an error.

Steve

-- 
Stephen Butler | Software Developer
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
Received on 2009-05-29 16:29:18 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.