-
Notifications
You must be signed in to change notification settings - Fork 140
Give Git a HOME on Windows #218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
HOME initialization was historically duplicated in many different places, including /etc/profile, launch scripts such as git-bash.vbs and gitk.cmd, and (although slightly broken) in the git-wrapper. Even unrelated projects such as GitExtensions and TortoiseGit need to implement the same logic to be able to call git directly. Initialize HOME in git's own startup code so that we can eventually retire all the duplicate initialization code. Signed-off-by: Karsten Blees <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
/submit |
Submitted as [email protected] |
This branch is now known as |
This patch series was integrated into pu via git@1ee5f93. |
This patch series was integrated into pu via git@2bb3fc8. |
This patch series was integrated into pu via git@191703e. |
This patch series was integrated into next via git@51c7e23. |
This patch series was integrated into pu via git@5d0c125. |
This patch series was integrated into pu via git@fc613d2. |
This patch series was integrated into next via git@fc613d2. |
This patch series was integrated into master via git@fc613d2. |
Closed via fc613d2. |
The environment variable
HOME
is a well-known concept on Unix/Linux, but not so much on Windows. In fact, there are competing concepts, and they fulfill separate roles.Let's try to map the closest that we can find to
HOME
so that Git is happy.Git for Windows carries this patch since 2015, so I think we're pretty sure that our chosen strategy works.