Skip to main content
replaced http://superuser.com/ with https://superuser.com/
Source Link

There was recently a questionquestion regarding the Windows 10 package manager built-in to PowerShell. It was called OneGet during the preview and so there is a [oneget][oneget] tag that exists.

The official name was changed to PackageManagement. Is there anything that needs to be done regarding the tag?

There was recently a question regarding the Windows 10 package manager built-in to PowerShell. It was called OneGet during the preview and so there is a [oneget] tag that exists.

The official name was changed to PackageManagement. Is there anything that needs to be done regarding the tag?

There was recently a question regarding the Windows 10 package manager built-in to PowerShell. It was called OneGet during the preview and so there is a [oneget] tag that exists.

The official name was changed to PackageManagement. Is there anything that needs to be done regarding the tag?

Tweeted twitter.com/#!/super_user/status/633352685199204352
Source Link
MC10
  • 10.5k
  • 11
  • 13

What to do about tag [oneget]?

There was recently a question regarding the Windows 10 package manager built-in to PowerShell. It was called OneGet during the preview and so there is a [oneget] tag that exists.

The official name was changed to PackageManagement. Is there anything that needs to be done regarding the tag?