Browse files

clarify context menu entry choice between cheetah and registry

Many users seem to get confused when asked to decide between
"Context menu entries" and "git-cheetah shell extension".

Since they want the context menu entries many will choose the registry
based ones since it explicitely talks about the context menu.

Lets talk about the same thing "context menu" and distinguish them by
calling them advanced and simple. To help existing users to recognize
these option from the previous installers mention the methods
(cheetah/registry) in brackets.

Signed-off-by: Heiko Voigt <>
  • Loading branch information...
1 parent 64bbe3d commit dfe44cd79269e1fa5b4cacf53f663eed97a6e32f Heiko Voigt committed Feb 6, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 share/WinGit/install.iss
@@ -48,10 +48,10 @@ Name: icons; Description: Additional icons; Types: custom
Name: icons\quicklaunch; Description: In the Quick Launch; Types: custom
Name: icons\desktop; Description: On the Desktop; Types: custom
Name: ext; Description: Windows Explorer integration; Types: custom
-Name: ext\reg; Description: Context menu entries; Flags: exclusive; Types: custom
+Name: ext\reg; Description: Simple context menu (Registry based); Flags: exclusive; Types: custom
Name: ext\reg\shellhere; Description: Git Bash Here; Types: custom
Name: ext\reg\guihere; Description: Git GUI Here; Types: custom
-Name: ext\cheetah; Description: git-cheetah shell extension; Flags: exclusive; Types: custom
+Name: ext\cheetah; Description: Advanced context menu (git-cheetah plugin); Flags: exclusive; Types: custom
Name: assoc; Description: Associate .git* configuration files with the default text editor; Types: custom
Name: assoc_sh; Description: Associate .sh files to be run with Bash; Types: custom
Name: consolefont; Description: {#COMP_CONSOLE_FONT}; Types: custom

0 comments on commit dfe44cd

Please sign in to comment.