Skip to content
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

[EXP] maintenance: fix bug, add headless-git.exe #313

Merged

Conversation

derrickstolee
Copy link
Collaborator

There is a bug that uses the wrong encoding in the current vfs-2.30.0* branches. This was fixed upstream but is still wrong here.

Also take the relevant commits from git-for-windows#2974 to add headless-git.exe to the installer and use that instead of git.exe to avoid a console window on the Windows platform.

derrickstolee and others added 3 commits February 8, 2021 10:18
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
On Windows, there are two kinds of executables, console ones and
non-console ones. Git's executables are all console ones.

When launching the former e.g. in a scheduled task, a CMD window pops
up. This is not what we want for the tasks installed via the `git
maintenance` command.

To work around this, let's introduce `headless-git.exe`, which is a
non-console program that does _not_ pop up any window. All it does is to
re-launch `git.exe`, suppressing that console window, passing through
all command-line arguments as-are.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
We just introduced a helper to avoid showing a console window when the
scheduled task runs `git.exe`. Let's actually use it.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obviously correct.

My only concern: shouldn't we prefer to merge v2.30.0.windows.2 right away?

@dscho
Copy link
Member

dscho commented Feb 8, 2021

My only concern: shouldn't we prefer to merge v2.30.0.windows.2 right away?

To answer my own question: this would not work, as there are merge conflicts between vfs-2.30.0 and v2.30.0.windows.2.

@derrickstolee derrickstolee merged commit 734057e into microsoft:vfs-2.30.0-exp Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants