I know that Explorer in Vista and Windows 7 no longer supports extensible column views, but is there any way to get those columns in Windows 7 or Vista. I don't mind using an alternate File Explorer, but not knowing things like what TAG or BRANCH I am on is becoming more and more annoying (having recently switched from XP to Windows 7).
R – Any way to get Tortoise Columns in Windows 7 or Vista
tortoisecvstortoisesvn
Related Solutions
I know many people who required a gentle introduction to cvs and ended up using WinCVS with no real difficulty. I know many others who are using the cvs client in Eclipse. This usage includes projects which are not otherwise managed by Eclipse. As for myself, I stick to the command-line myself because I feel the lack of GUI abstractions helps me to always understand exactly what CVS is doing. All three solutions work well on Vista, 32 and 64 bit. Our shop uses Mac, Linux, Solaris, and Windows, with the server on a Linux machine, and we never have any problems with compatibility.
There's one issue you should be aware of regardless of your choice of cvs client for cross-platform goodness, though. Most cvs clients convert between Unix newlines (on the server) and Windows newlines (on the client) by default. You should understand that this conversion is happening and be aware of the consequences.
- This conversion will cause real problems if you try to commit a file with Unix newlines. So, you need to avoid, for example, copying files from a Unix repository to your Windows box, editing them, and committing them unless you've done the newline conversion. We had some real problems with this in my shop, and I instituted a strict policy that people should only communicate files between machines by committing them to CVS. Never, for example, by email, shared network directories, etc.
- If your CVS repository has any binary files, some may not have been properly tagged as binary files. In *nix-only shop, nobody would notice, as the binary flag won't affect most binary files. But in a cross-platform shop, the binary flag routinely affects how cvs treats files, since it will disable any attempts at newline conversion. Typically, any file which was committed from a Unix box will be correctly represented in the repository, so you can fix the problem on the Windows end by merely changing the tag and re-updating. I.e.,
cvs admin -kb file
cvs update -A file
If it is the first time they connected, it doesn't matter if there's a mismatch... the client just had some unrelated old entry that happened to have the same host name or ip address associated with it. Just clear it with:
ssh-keygen -R $name_or_ip
After you do that, it should certainly say whether it is RSA, ECDSA, etc. the next time you connect. If not, try using a proper client like the OpenBSD OpenSSH client which is standard on Linux, or trying -v (or -vvvv, etc. verbose options). And then verify and accept the new key. The key fingerprint format in old clients is md5 (and in new ones is sha256, in some weird base64 format instead of ascii-hex), and the right way to get the fingerprint on the server side is:
ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key
Best Answer
I don't think it's going to be implemented in a foreseeable future. The idea of using a third-party file explorer is not bad but TortoiseSVN is a Windows shell extension and I don't think they'll take the path of writing plugins for alternative file browsers.
The subversion site lists a number of clients. Some of them are GUI tools and implement their own file browsers (for instance, RapidSVN). It can be an alternative and, of course, they don't need to fully replace TortoiseSVN.