build icon indicating copy to clipboard operation
build copied to clipboard

Remember INSTALLDIR on upgrade

Open mxmauro opened this issue 3 years ago • 10 comments

When Go is upgraded on Windows, the previous installation location is not reused.

Installation directory is already stored in registry so half of the work is already done. The added elements retrieves the info from registry and updates INSTALLDIR.

mxmauro avatar Jan 30 '21 02:01 mxmauro

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

google-cla[bot] avatar Jan 30 '21 02:01 google-cla[bot]

@googlebot I signed it!

mxmauro avatar Jan 30 '21 02:01 mxmauro

This PR (HEAD: 9d7665bd1a64d8c3bdc0bb4c217d74a4ea4038c0) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/build/+/288252 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off) See the Wiki page for more info

gopherbot avatar Jan 30 '21 02:01 gopherbot

Message from Go Bot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps: A maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Jan 30 '21 02:01 gopherbot

Message from Alexander Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Feb 02 '21 16:02 gopherbot

Message from Alexander Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Feb 02 '21 16:02 gopherbot

Message from Mauro Leggieri:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Feb 02 '21 17:02 gopherbot

Message from Alexander Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Nov 08 '21 11:11 gopherbot

Message from Alexander Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Nov 08 '21 11:11 gopherbot

Message from Mauro Leggieri:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Nov 08 '21 11:11 gopherbot

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps: A maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Sep 25 '23 15:09 gopherbot

Message from Jenny Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Sep 25 '23 15:09 gopherbot

Message from Jenny Rakoczy:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Sep 25 '23 15:09 gopherbot

Message from Mauro Leggieri:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/288252. After addressing review feedback, remember to publish your drafts!

gopherbot avatar Sep 25 '23 15:09 gopherbot