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

Feat/update scheduler v2 #155

Merged

Conversation

bufferoverflow
Copy link
Contributor

This replaces #153 and uses git http.proxy settings as suggested by @dscho

@@ -5,6 +5,13 @@
# when confirmation to do so is given.

git_update () {
proxy=$(git config --get http.proxy)
if test "$proxy" != ""

This comment was marked as off-topic.

proxy=$(git config --get http.proxy)
if test "$proxy" != ""
then
export https_proxy="http://$proxy"

This comment was marked as off-topic.


[UninstallRun]
Filename: "schtasks"; \
Parameters: "/Delete /F /TN ""Git for Windows Updater"""; \

This comment was marked as off-topic.

@dscho dscho force-pushed the feat/update-scheduler-v2 branch from 2ad7207 to debc320 Compare September 8, 2017 22:34
Signed-off-by: Roger Meier <[email protected]>
Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho force-pushed the feat/update-scheduler-v2 branch from debc320 to df85f0c Compare September 8, 2017 22:36
@dscho
Copy link
Member

dscho commented Sep 8, 2017

Thank you!

I actually just realized that I can force-push updates to your branch, so i just went ahead and made the modifications myself. While at it, I also redirected a couple more messages to stderr.

@dscho dscho merged commit cbcc28c into git-for-windows:master Sep 8, 2017
dscho added a commit that referenced this pull request Sep 8, 2017
The Git installer now offers [an option to keep Git
up-to-date](#155).

Signed-off-by: Johannes Schindelin <[email protected]>
@bufferoverflow
Copy link
Contributor Author

@dscho Thank so much!

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