SmartSVN 7
A new release of SmartSVN is available!
We are proud to announce the release of SmartSVN 7 (codename: "dormouse"): finally, more than 7 months after the official Subversion 1.7 release, SmartSVN now also supports the SVN 1.7 working copy format — a "Thank you" to all of our users for their patience!
SmartSVN is a graphical client for the Open Source version control system Subversion (SVN) and runs on all major operating systems, including Windows, Mac OS X and Linux. SmartSVN is aimed at professionals who demand a reliable, efficient and well-supported SVN client for their daily business.
SmartSVN 7 supports the new Subversion 1.7 working copy format and comes with a couple of smaller improvements that are listed in the change log.
Download SmartSVN 7
SmartGit: upgrading to msysGit 1.7.10 (or higher)
How to upgrade repositories to msysGit 1.7.10 (or higher) when having non-ASCII file names
Since msysGit 1.7.10, file names are stored using UTF-8 encoding internally. This finally makes repositories containing file names with non-ASCII characters compatible to other operating systems, especially Mac OS and Linux. Unfortunately, non-ASCII file names which have been added with older msysGit versions will cause problems immediately after the upgrade and need to be fixed:
For working trees which are clean with msysGit 1.7.9 and earlier versions ('clean' means that neither SmartGit nor 'git status' shows any changes), file names containing non-ASCII characters will now show up as unversioned in SmartGit. At the same time, there will be a corresponding missing file showing up with '?'-characters. git status will only show the unversioned file, what actually exposes the same problem. To continue working with such a repository and at the same time make it compatible with other platforms, such file names have to be converted to UTF-8. Following example illustrates how this is done for a test repository which contains one file called 'ä.txt':
The repository is clean when invoking 'git status' using msysGit 1.7.9, however using msysGit 1.7.10, gives:
> git status# On branch master
# Untracked files:
# (use "git add
#
# "\303\244.txt"
nothing added to commit but untracked files present (use "git add" to track)
In a first step we will use msysGit 1.7.9 to temporarily remove the file from the repository (i.e. you will still need a working installation of msysGit 1.7.9 to perform following step):
> git-1.7.9 rm --cached ä.txtrm '?.txt'
Now, we will use msysGit 1.7.10 (or higher) to re-add the file:
> git add ä.txt'git status' now properly shows the rename:
> git status# On branch master
# Changes to be committed:
# (use "git reset HEAD
#
# renamed: "\344.txt" -> "\303\244.txt"
#
Finally, we will commit the conversion:
> git commit -m "File names converted to UTF-8."[master 6286cb7] File names converted to UTF-8.
1 file changed, 0 insertions(+), 0 deletions(-)
rename "\344.txt" => "\303\244.txt" (100%)
Now SmartGit will show a clean working tree as well. If the repository has been cloned from a central remote, the commit should be pushed and other Git Windows users should be informed that they need to upgrade to msysGit 1.7.10 as well, so they will see correct file names after checking out the commit. If they should encounter problems when trying to check out the commit, it may be necessary to use Local|Reset with Hard option to reset to this commit.