« Previous - Version 18/116 (diff) - Next » - Current version
Sickboy, 01/28/2009 10:29



Recommended Clients

Other Clients

  • MsysGit (CmdLine+Advanced GUI)
  • Cygwin Git (only required on Windows for repositories with > 2GB Pack files

Experimental Clients


  • Install Putty Suite
  • Install MSysGit (2GB Fixed Edition!)
    • Choose to use Plink for SSH
    • Choose to install for Windows Command Line (Middle option, out of 3)
  • Edit your path and add the path/to/git/bin (Control Panel, System, Advanced, Environment Variables, Path), e.g: C:\Program Files (x86)\Git\Bin
  • Install GitExtensions (Don't install the FullSetup, or if you do, please do not install the included MSysGit with it!!)
    • Incase of 64-bit, also download the .zip file, unpack the GitExtensionsShell.dll, rename it to GitExtensionsShellEx32.dll and place it in your Git Extensions installation folder. Then: regsvr32 GitExtensionsShellEx32.dll from a dos prompt
  • Startup the Git Extensions application, and verify that all settings are okay


  • User + Email Settings: You can use Git Extensions Settings for this
  • AutoCRLF Disable: You can use the git config --system or --global command, e.g: git config --system core.autocrlf false

Initial Steps

  • Create a Key Set with PuttyGen (Part of the putty suite) or ssh-keygen (If you don't use a password, you can autoload the key in pageant, but it is also less secure)
  • Send PUBLICkey to admin (Guard the PRIVATEkey with your life! :D)
  • Load your PRIVATEkey into the PageAnt application (Part of putty suite)
  • Make a connection with putty, to git.6thsense.eu
    • Click YES/Accept to accept the server key
    • Close putty again
  • Use interface or cli git: git clone :REPOSITORYNAME.git (Receive repository name from admin)
    • In case of message: "The server's host key is not cached in the registry. You
      have no guarantee that the server is the computer you
      think it is.", press y


  • In Git, you have a local copy of the repository
  • If you commit, you only commit to your local repository. If you want to push your changes to the shared remote repository, you must first git pull, and then git push
  • If you wish to fetch, you use git pull
  • If there are things to merge, like changes to files by 2 persons, use git merge
  • every git command can be used with --help for basic help output
  • If you wish to look at the log using the GIT Gui on your repository, you can check the Repository Menu, and Visualize master's history (or all branches)

Git use


Virtual Folders / Working with Repositories in ArmA

RM knowledge



EditTickerHeader01.jpg (109.7 kB) admin, 07/25/2011 08:49

EditTickerHeader02.jpg (75.5 kB) admin, 07/25/2011 08:49

EditTickerHeader03.jpg (87.5 kB) admin, 07/25/2011 08:49

EditTickerHeader04.jpg (92.6 kB) admin, 07/25/2011 08:49

EditTickerHeader05.jpg (81.7 kB) admin, 07/25/2011 08:49

devheaven_permission_report_2013_11_27.pdf (83.7 kB) kju, 11/27/2013 10:14