Download Git Mac

Git mac free download. Git-osx-installer This is the official. THE LATEST CODE IS AVAILABLE IN THE GIT REPOSITORIES. Use the 'Download Snapshot' button at the top. Open Safari and browse to the Git developer site. Click on Mac OS X below Downloads. Open the git-2.8.1-intel-universal-mavericks file in your Downloads folder. Double click the.

• FAT universal binary includes ppc, ppc64, x86 and x86-64
• Mac OS X 10.4.8 and later compatible
  (including 10.5.x, 10.6.x, 10.7.x, 10.8.x, 10.9.x, 10.10.x, 10.11.x etc.)
• Git translations included!
• git send-email and git imap-send work out-of-the-box, nothing more to install!
• git instaweb works out-of-the-box and includes several enhancements
• --perl-regexp is fully supported
• git subtree included
• git-credential-osx-keychain included
• Git 2.8.0 and later’s http.[<url>.]pinnedpubkey option is fully supported
• Full documentation included (man pages, html pages, pdf, release notes, howtos, tech docs etc.)
• GnuPG gpg signing utility with smart card support included!

Quick Download

Important Notes

In order to fully support SHA-256 certificates on Mac OS X 10.4 and Mac OS X 10.5 and to be more fully integratedwith the native OS X experience, this version of Git uses libcurl for all http/https/imap/imaps/smtp/smtps activitywhere libcurl has been compiled to use the OS X native Secure Transport instead of OpenSSL. (This means that Git will usethe standard root certificates from the normal system keychain locations for https/smtps/imaps authentication unless oneof the various Git certificate configuration options is used to tell it otherwise.) Please note that even though libcurl is using the OS X native Secure Transport backend, the Secure Transport backend has been enhanced so that it does not suffer from the client certificate indigestion problem.

In practice there should be no difference in use between Git built this way and Git built to use curl/OpenSSL with oneminor exception.

Secure Transport does not support a directory of certificates like OpenSSL does. An error will result if any ofthe following are used:

• http.sslCAPath (but http.sslCAInfo works just fine)
• GIT_SSL_CAPATH (but GIT_SSL_CAINFO works just fine)
• sendemail.smtpsslcertpath set to a directory (but set to a file works just fine)
• smtp-ssl-cert-path set to a directory with git send-email (but set to a file works just fine)

Additionally since the version of git imap-send that’s included is a curl-only version, there is one tinybehavioral difference to be aware of. When git imap-send is set to use a tunnel (i.e. imap.tunnel is set),an OpenSSL-using version of git imap-send will attempt to use the STARTTLS command if the other end ofthe tunnel supports it. A libcurl-using version of git imap-send will never do this. This only affects tunnels. Alldirect connections using imaps will always be encrypted.

Starting with Git version 2.8.0, an http.[<url>.]pinnedpubkey option is available.It may be set to any value supported by cURL’sCURLOPT_PINNEDPUBLICKEY option and, in addition, this version also allows it to be set to a filename ofa PEM or DER format certificate (in which case the public key is automatically extracted from the certificate) and,in the case of a PEM format file, one or more PEM format public keys and/or certificates may be combined (by simplyconcatenating them together) to form a public key pinning set similarly to the way multiple “sha256//…”values can be combined to form a public key pinning set (by concatenating them with a “;”separator).

A change log showing the various software versions and patches included in the different releases is availablehere.

Despite the name of this installer including “OS X” in its title, it supports OSversions 10.4.8 and later no matter what Cupertino’s current nom-du-jour for the OS happens to be –“Mac OS X”, “OS X”, “macOS” etc.

Git Translations

The Git translations ARE included. The installer also contains an option (off by default) to make the installedversion of Git choose its translation based on the System Preferences > International > Languages settings(instead of the LANG etc. environment variables) if desired.

Details on how to alter the translation selection behavior can be found in the release notes (installed to /opt/git/Release_Notes.rtf).

Optional Extras

Optional installs of TopGit, a curl command linetool (that uses the libcurl.dylib installed for Git), GnuPG’sgpg utility and library headers (so that a new version of Git can be built from source using thelibraries installed for Git) are included in the installer and enabled by default.

Customize the installation to turn off any of the optional installs.

Details on what gets installed and where everything goes can be found in the release notes (installed to /opt/git/Release_Notes.rtf).

Mac Download For Pc

Patch Sources

Various patches have been applied in order to make the build work well with Mac OS X. They are all availablefrom the Git OS X Installer repository and theREADME_PATCHES.txt filedetails them all.

Downloads

Download Git Flow Mac

NOTE: The hashes shown below have been signed by a GPG key. Instructions for verifying the hashesusing the key can be found in the hashes.txt file.

Universal binary installers of Git (including required support libraries and executables)runnable on Mac OS X 10.4 or later are available from the following convenient download links:

Please note that older versions which were previously listed here, while they may still be available fordownload, are no longer recommended.

License

Git itself is licensed under GPLv2. Some of the libraries it has been linked with have less restrictive licenses,but since GPLv2 is the most restrictive of the bunch it’s the controlling one. GnuPG is licensed underGPLv3 but is an optional install (aggregated into the installer) and does not affect the license used by Git.GnuPG is linked with libusb and libusb-compat to provide smart card support and those are LGPLv2.1 making theeffective GnuPG license restrictions still GPLv3.

The installer will display ALL licences for all software included in the installer package.

See Also

• The GNU General Public License v2.0
• The GNU General Public License v3.0

The 'clone' command downloads an existing Git repository to your local computer.

You will then have a full-blown, local version of that Git repo and can start working on the project.

Typically, the 'original' repository is located on a remote server, often from a service like GitHub, Bitbucket, or GitLab). That remote repository's URL is then later referred to as the 'origin'.

Important Options

<repository>

Specifies the URL of the remote repository. Usually, this will point to a remote server, using a protocol like HTTP, HTTPS, SSH, or GIT.

<directory>

The name of the folder on your local machine where the repository will be downloaded into. If this option is not specified, Git will simply create a new folder named after the remote repository.

--recurse-submodules

Clones and initializes all contained submodules. If your project contains submodules, using this parameter will make sure that all submodules will both be cloned and initialized once the main project has been cloned. This saves you from having to manually initialize and update the submodules later.

The Git Cheat Sheet

No need to remember all those commands and parameters: get our popular 'Git Cheat Sheet' - for free!

Usage Examples

In its simplest (and most common) form, only the repository URL is specified:

This will download the project to a folder named after the Git repository ('git-crash-course' in this case). If you want a different folder name, simply specify it as the last parameter:

Tip

Simple Cloning in Tower

In case you are using the Tower Git client, cloning a project becomes easy as pie. You can connect your GitHub / GitLab / Bitbucket / or other remote accounts with Tower - and from then on simply clone with a single click!

Learn More

Download Git Desktop Mac

• Check out the chapter Starting with an Existing Project in our free online book
• Find the full command description in the Git documentation
• More frequently asked questions about Git & version control