<simplesect>\r
<para>\r
This appendix contains solutions to problems/questions you might\r
- have when you are responsible for deploying TortoiseSVN to multiple\r
+ have when you are responsible for deploying TortoiseGit to multiple\r
client computers.\r
</para>\r
</simplesect>\r
<sect1 id="tsvn-admins-grouppolicies">\r
- <title>Deploy TortoiseSVN via group policies</title>\r
+ <title>Deploy TortoiseGit via group policies</title>\r
<indexterm>\r
<primary>group policies</primary>\r
</indexterm>\r
<primary>deploy</primary>\r
</indexterm>\r
<para>\r
- The TortoiseSVN installer comes as an MSI file, which means you\r
+ The TortoiseGit installer comes as an MSI file, which means you\r
should have no problems adding that MSI file to the group policies\r
of your domain controller.\r
</para>\r
</ulink>.\r
</para>\r
<para>\r
- Versions 1.3.0 and later of TortoiseSVN must be installed under\r
+ Versions 1.3.0 and later of TortoiseGit must be installed under\r
<emphasis>Computer Configuration</emphasis> and not under\r
<emphasis>User Configuration</emphasis>. This is because those versions\r
need the new CRT and MFC DLLs, which can only be deployed <emphasis>per\r
computer</emphasis> and not <emphasis>per user</emphasis>.\r
- If you really must install TortoiseSVN on a per user basis, then you must\r
+ If you really must install TortoiseGit on a per user basis, then you must\r
first install the MFC and CRT package version 8 from Microsoft on each\r
- computer you want to install TortoiseSVN as per user.\r
+ computer you want to install TortoiseGit as per user.\r
</para>\r
</sect1>\r
<sect1 id="tsvn-admins-upgradecheck">\r
<primary>version</primary>\r
</indexterm>\r
<para>\r
- TortoiseSVN checks if there's a new version available every few days.\r
+ TortoiseGit checks if there's a new version available every few days.\r
If there is a newer version available, a dialog shows up informing\r
the user about that.\r
</para>\r
to show up so your users don't go and upgrade immediately.\r
</para>\r
<para>\r
- Versions 1.4.0 and later of TortoiseSVN allow you to redirect that upgrade\r
+ Versions 1.4.0 and later of TortoiseGit allow you to redirect that upgrade\r
check to your intranet server. You can set the registry key\r
- <filename>HKCU\Software\TortoiseSVN\UpdateCheckURL</filename> (string value)\r
+ <filename>HKCU\Software\TortoiseGit\UpdateCheckURL</filename> (string value)\r
to an URL pointing to a text file in your intranet. That text file must have\r
the following format:\r
<screen>\r
1.4.1.6000\r
-A new version of TortoiseSVN is available for you to download!\r
-http://192.168.2.1/downloads/TortoiseSVN-1.4.1.6000-svn-1.4.0.msi\r
+A new version of TortoiseGit is available for you to download!\r
+http://192.168.2.1/downloads/TortoiseGit-1.4.1.6000-svn-1.4.0.msi\r
</screen>\r
The first line in that file is the version string. You must make sure that\r
- it matches the exact version string of the TortoiseSVN installation package.\r
+ it matches the exact version string of the TortoiseGit installation package.\r
The second line is a custom text, shown in the upgrade dialog. You can write\r
there whatever you want. Just note that the space in the upgrade dialog is\r
limited. Too long messages will get truncated!\r
<primary>ASP projects</primary>\r
</indexterm>\r
<para>\r
- As of version 1.4.0 and later, the TortoiseSVN installer doesn't provide\r
+ As of version 1.4.0 and later, the TortoiseGit installer doesn't provide\r
the user with the option to set the <literal>SVN_ASP_DOT_NET_HACK</literal>\r
environment variable\r
anymore, since that caused many problems and confusions with users which\r
</para>\r
<para>\r
But that option is only hidden for the user. You still can force the\r
- TortoiseSVN installer to set that environment variable by setting the\r
+ TortoiseGit installer to set that environment variable by setting the\r
<literal>ASPDOTNETHACK</literal>\r
property to TRUE. For example, you can start the installer like this:\r
<screen>\r
-msiexec /i TortoiseSVN-1.4.0.msi ASPDOTNETHACK=TRUE\r
+msiexec /i TortoiseGit-1.4.0.msi ASPDOTNETHACK=TRUE\r
</screen>\r
</para>\r
</sect1>\r
<primary>group policies</primary>\r
</indexterm>\r
<para>\r
- As of version 1.5.0 and later, TortoiseSVN allows you to disable (actually, hide)\r
+ As of version 1.5.0 and later, TortoiseGit allows you to disable (actually, hide)\r
context menu entries. Since this is a feature which should not be used lightly\r
but only if there is a compelling reason, there is no GUI for this and it has\r
to be done directly in the registry.\r
This can be used to disable certain commands for users who should not use them.\r
But please note that only the context menu entries in the <emphasis>explorer</emphasis>\r
are hidden, and the commands are still available through other means, e.g. the\r
- command line or even other dialogs in TortoiseSVN itself!\r
+ command line or even other dialogs in TortoiseGit itself!\r
</para>\r
<para>\r
The registry keys which hold the information on which context menus to show are\r
- <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename>\r
- and <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.\r
+ <filename>HKEY_CURRENT_USER\Software\TortoiseGit\ContextMenuEntriesMaskLow</filename>\r
+ and <filename>HKEY_CURRENT_USER\Software\TortoiseGit\ContextMenuEntriesMaskHigh</filename>.\r
</para>\r
<para>\r
Each of these registry entries is a <literal>DWORD</literal> value, with each\r
</screen>\r
The lower <literal>DWORD</literal> value (<literal>0x80080000</literal>)\r
must then be stored in\r
- <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskLow</filename>,\r
+ <filename>HKEY_CURRENT_USER\Software\TortoiseGit\ContextMenuEntriesMaskLow</filename>,\r
the higher <literal>DWORD</literal> value (<literal>0x20000000</literal>) in\r
- <filename>HKEY_CURRENT_USER\Software\TortoiseSVN\ContextMenuEntriesMaskHigh</filename>.\r
+ <filename>HKEY_CURRENT_USER\Software\TortoiseGit\ContextMenuEntriesMaskHigh</filename>.\r
</para>\r
<para>\r
To enable the menu entries again, simply delete the two registry keys.\r
OSDN Git Service
