Ph: 212143237116
4 Responsed To This Post
Subsribes to this topic Comment RSS or TrackBack URL
mygif_alt
Stefan Says, in 6-10-2007 at 12:30:28 from 194.208.64.49    

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.

mygif
varun krishnan Says, in 6-10-2007 at 13:20:20 from 122.164.57.54    

@Stefan

Thanks for the tip buddy.

Works fine

mygif_alt
Szymon Says, in 6-10-2007 at 14:31:31 from 83.238.116.6    

.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.

mygif
The expert Says, in 6-10-2007 at 16:34:31 from 212.143.237.116    

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.

Leave A Reply

 Username (*required)

 Email Address (*private)

 Website (*optional)

Inform me when someone post new message here

Please Note: Comments Moderation maybe active so there is no need to resubmit your comment
Web Analytics


You are viewing a mobilized version of this site...
View original page here

Mobilized by Mowser Mowser
Mobilytics