No, if you try to add Elf, at least with TSVN, the .svn directories are
read and the tool assumes it's already in the repository.
What if you created a new method of copying? Do you think that'd work?
For instance, what about creating an item in the Send To menu for
copying files. It would simply be a batch file of some sort to copy the
selected files/directories to a new location without the .svn
directories. Either that or something to strip out the .svn directories
after the copy. Would that work? I don't think that'd be too much work
Honestly, the autoversioning stuff sounds like one of the best
solutions. I've never seen/heard of it before; but it's something I'd
like to look into, now.
From: Joshua Varner [mailto:firstname.lastname@example.org]
Sent: Friday, September 02, 2005 2:09 PM
To: Flanakin Michael C Ctr HQ OSSG/OMR
Subject: Re: .svn folder needs to go away?
On 9/2/05, Flanakin Michael C Ctr HQ OSSG/OMR
I wasn't asking how to checkout a repository to a different
directory. What I was referring to was this...
(a) You have http://host/repo/trunk/Characters checked out to
(b) You copy-paste (via the OS) Chars/Ogre to Chars/Elf
Chars/Elf <-- points to Characters/Ogre
Chars/Elf/Textures <-- points to Characters/Ogre/Textures
The problem I mentioned was that I don't like the fact that,
.svn directories are copied too, Svn doesn't recognize a problem
the previous structure. Chars/Ogre and Chars/Elf will both be
with Characters/Ogre. This is the problem. He's asking for a way
copy the .svn directories so Svn recognizes them as new
files/directories. My suggestion was to remove .svn dirs after
copy-paste or use the export command.
What if step three is
(c) svn add Elf
Should that wipe out an svn folders under Elf (possibly with --force)?
I think that is a reasonable behavior, even if possibly less effecient
than the svn copy. Or if the svn folders come from the same repos
should they do an svn copy under the covers?
Received on Tue Sep 6 14:06:40 2005