" If it can't find a system git install it will, depending on situation, download and install an embedded copy or prompt the user to manually find the git.exe." Regarding my remaining question, you made this statement. Thank you! It does clearly answer the first of my two questions. Sourcetree should accept any 1.x or 2.x version of Git.
Sourcetree git windows#
So, provided the SDK folder structure mirrors that of Git for Windows release, if you point Sourcetree at C:\git-sdk-64\cmd\git.exe it should use it. If it does it checks the git version and if all is good it will configure itself to use and remember that Git install. If it can't find a system git install it will, depending on situation, download and install an embedded copy or prompt the user to manually find the git.exe.īecause the user might find bin/git.exe or one of the others, when Sourcetree is presented with a git.exe it will attempt to walk the local folder structure to find cmd/git.exe known install folders in c:\program files*\.When Sourcetree starts it tries to find a system install of git by looking for a git.exe in Sourcetree expects to use the cmd/git.exe version of git.exe. However this information may be of use to you and others. So the short answer is we don't formally support that style of Git install, we have a similar arms length approach to Cygwin installs of Git. As far as I know, even when two copies of an application are identical, there still might be different implications for choosing one or the other, for example, if SourceTree expects certain other files to be present in the same directory as the git.exe application it wants to know about. Yet, even if two choices are identical files, I do not know whether or not there are unexpected ramifications of choosing one or the other. (The other two applications in the list of six are each unique.Ĭ:\git-sdk-64\cmd\git.exe is by far the smallest andĬ:\git-sdk-64\usr\src\git\git.exe is by far the largest.) Likewise, these two applications are also binary identical with each other (but different from the previous two). Regarding my first question, I will point out that the git.exe applications in these two locations are currently binary identical. I'm trying to use SourceTreeSetup-2.3.1.0.exe, which I downloaded fresh from just to be sure it was the very latest. Is there any way at all in the SourceTree Tools / Options for Git to say, "Let me point you to Git"? I see only the options of Embedded or else the choice it's made of LibGit2Sharp. NET)! I see no way to tell it that I want to point it to a different location of Git. However, at the moment, after the latest reinstall of SourceTree, it seems to just assume I'm using system Git that is "LibGit2Sharp" (an interface to libgit2 for Visual Studio. Even supposing it wants to know where git.exe is, which of the following possibilities might be the one most appropriate for SourceTree's need?Ĭ:\git-sdk-64\mingw64\libexec\git-core\git.exeĢ) Since I had been observing fragile behavior and failures on startup for the new SourceTree, I thought I would try making a different selection than I did previously. I have two related questions about getting the new SourceTree to properly use Git from the Git for Windows SDK.ġ) Sometimes during installation SourceTree admits it doesn't recognize where Git is on the system. I've been using the older versions of SourceTree with the GfW SDK for a very long while before now.) (This did not seem to be a problem in the past.
Sourcetree git how to#
It seems that when installing SourceTree, it now has trouble finding or recognizing how to use Git when it is located in an install of the Git for Windows SDK. Optionally, instead of just installing Git for Windows, one may install the Git for Windows SDK, which also provides the MSYS2+MinGW Linux build environment integrated with Windows. That great application is built upon the Git for Windows SDK. Most Git users on Windows are probably using Git for Windows.
0 kommentar(er)
