TortoiseGit (https://tortoisegit.org/) added basic support for git-svn in release 0.8.1.0: The release log says: Add Basic Git-SVN Operation: Add SVN DCommit Command Add “SVN Rebase” and “SVN DCommit” command at shell contextmenu Support Git svn-clone at clone dialog.
Check out svndumpfilter and this section on Repository Maintenance. Once you have a dumpfile for the entire old repository, you can use svndumpfilter to extract just the portion that you want. I am not aware of a way to do this with TortoiseSVN.
Check the TortoiseSVN Manual: TortoiseMerge | Colour Settings Page. This is the default color scheme (see it in TortoiseMerge | File | Settings | Colors): It also makes sense to know the line status icons meaning.
Current versions of TortoiseSVN do not install command-line SVN client by default. You’ll have to: Select it explicitly in the installer (see comment by Stefan) Download it and install it separately from http://subversion.apache.org/packages.html.
Currently I have the following in my Global Ignore Pattern: bin obj CVS .cvsignore *.user *.suo Debug Release *.pdb test.* Thumbs.db Works really well to ignore several hidden or temp files/folders…. So for your specific requirements: Folders: bin obj release compile Files: *.bak *.user *.suo I would use: bin obj release compile *.bak *.user *.suo
Subversion 1.5.x adds a lot of svn:mergeinfo properties, even on files/folders which you think have nothing to do with the merge. But Subversion still uses those to reduce the merge time for subsequent merges. If you don’t like those, you can safely remove those modified/added svn:mergeinfo properties from all files/folders which were not part of … Read more
Though a couple of correct answers have already been provided, I want to point out that there are several more techniques one may use to see where you are in Subversion. Here is the complete list: Windows Explorer — Windows Explorer has the flexibility to add columns from a large set of choices beyond the … Read more
Did you enable AnkhSVN in Tools->Options->Source Control? When it is the default SCC provider it should automatically detect that your (C# ?) website project is already in Subversion.
svn export is the command you’re looking for. You can export a controlled set of files to a non-controlled location and use that.
As I see it, the big difference is that checkout creates a working copy, whereas update brings down changes to an existing working copy.