git-extra: link executables as terminal server aware#429
Conversation
|
Hmm. Seems as if there is a new problem: apparently |
dscho
left a comment
There was a problem hiding this comment.
Apart from the build failure, the change looks good to me, but I haven't really completely wrapped my head around the implications of that tsaware flag yet.
I'll take a look. |
Whith Windows 2000, Microsoft introduced a flag to the PE header to mark executables as "terminal server aware". Windows terminal servers provide a redirected Windows directory and redirected registry hives when launching legacy applications without this flag set. Since we do not use any INI files in the Windows directory and don't write to the registry, we don't need this additional preparation. Telling the OS that we don't need this should provide slightly improved startup times in terminal server environments. This partially addresses git-for-windows/git#3935 Signed-off-by: Matthias Aßhauer <mha1993@live.de>
5634b80 to
60053bf
Compare
|
Ok, I've got it to build again. I had messed up some of the makefile syntax. |
Git's executables are [now](#429) marked [Terminal Server-aware](git-for-windows/git#3942), meaning: Git will be slightly faster when being run using Remote Desktop Services. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
|
The updated |
The build was successful. Before I synchronize |
|
The newest snapshot has these changes. |
With Windows 2000, Microsoft introduced a flag to the PE header to mark executables as
"terminal server aware". Windows terminal servers provide a redirected Windows directory and
redirected registry hives when launching legacy applications without this flag set. Since we
do not use any INI files in the Windows directory and don't write to the registry, we don't
need this additional preparation. Telling the OS that we don't need this should provide
slightly improved startup times in terminal server environments.
This partially addresses git-for-windows/git#3935