Comments on: Why SubVersion SVN can be a pain

By: The expert

The expert — Sun, 10 Jun 2007 11:04:31 +0000

So stupid reason to blame svn,
for the completely not related things.

- you can use the FTP client that ignores hidden folders
(.svn are always hidden)
- you can use svn export as it is written above
- you can use a command line that does not copy .svn
- you can organize the web site as a working copy
and just call svn update on the web-server site.
There are lot of references on how to use svn as the web-site deployment tool.

By: Szymon

Szymon — Sun, 10 Jun 2007 09:01:31 +0000

.svn files are a pain even if you are using export. You have to perform so many actions just to upload your code changes. Fortunately there are smart SVN hosting options like springloops that makes things much easier. Give it a try, maybe it will work for you.

By: varun krishnan

varun krishnan — Sun, 10 Jun 2007 07:50:20 +0000

@Stefan

Thanks for the tip buddy.

Works fine

By: Stefan

Stefan — Sun, 10 Jun 2007 07:00:28 +0000

With TortoiseSVN, you don’t really need that context menu because you already have one!
You can right-drag the working copy folder to another location, and then choose “SVN Export here…” from the context menu.
See here for more details about the right-drag handler in TortoiseSVN:
http://tortoisesvn.net/most-forgotten-feature

An ‘export’ creates a copy of the working copy without all the .svn folders, and I think that’s what you want/need in your situation.