satyan@redmond:~/src$ git checkout -b microsoft-acquisitions Switched to a new branch 'microsoft-acquisitions' satyan@redmond:~/src$ scp email@example.com:/github . satyan@redmond:~/src$ git add github satyan@redmond:~/src$ git commit -m "Microsoft announced in June that it > was buying the Git repository and collaboration platform GitHub for > $7.5 billion in stock. That acquisition has received all the necessary > regulatory approvals, and has now completed. Nat Friedman, formerly of > Xamarin, will take the role as GitHub CEO on Monday. > > The news of the acquisition sent ripples around the open source world, > as GitHub has become the home for a significant number of open source > projects. We argued at the time that the sale was likely one of > necessity, and that of all the possible suitors, Microsoft was the best > one, due to common goals and shared interests. Friedman at the time > sought to reassure concerned open source developers that the intent was > to make GitHub even better at being GitHub, and that he would work to > earn the trust of the GitHub community. Those views were reiterated > today. > > Since then, Microsoft has joined the Open Invention Network, a patent > cross-licensing group that promises royalty free licenses for any patents > that apply to the Linux kernel or other essential open source packages. > This was a bold move that largely precludes Redmond from asserting its > patents against Android, and should mean that the company will no longer > receive royalties from smartphone manufacturers. > > Sources close to the matter tell us that Microsoft's decision to join > OIN was driven in no small part by the GitHub acquisition. GitHub is > already a member of OIN, which left Microsoft with only a few options: > withdraw GitHub from OIN, a move that would inevitably upset the open > source world; acquire GitHub as some kind of arm's length subsidiary > such that GitHub's OIN obligations could not possibly apply to > Microsoft; or join OIN too, as the most straightforward approach that > also bolstered the company's open source reputation. Microsoft took > the third option." [microsoft-acquisitions baadf00d] Microsoft announced... 1 file changed, billions of insertions(+), 0 deletions(-) satyan@redmond:~/src$ git checkout microsoft-corp Switched to branch 'microsoft-corp' satyan@redmond:~/src$ git merge microsoft-acquisitions Updating cafef00d..baadf00d Fast-forward billions-of-files | billions ++++++++++++ satyan@redmond:~/src$ git branch -d microsoft-acquisitions
Archive for the ‘git’ Category
It's fair to say that the Windows 10 October 2018 Update has not been Microsoft's most successful update. Reports of data loss quickly emerged, forcing Microsoft to suspend distribution of the update. It has since been fixed and is currently undergoing renewed testing pending a re-release.
This isn't the first Windows feature update that's had problems—we've seen things like significant hardware incompatibilities in previous updates—but it's certainly the worst. While most of us know the theory of having backups, the reality is that lots of data, especially on home PCs, has no real backup, and deleting that data is thus disastrous.
Windows as a service
Microsoft's ambition with Windows 10 was to radically shake up how it develops Windows 10. The company wanted to better respond to customer and market needs, and to put improved new features into customers' hands sooner. Core to this was the notion that Windows 10 is the "last" version of Windows—all new development work will be an update to Windows 10, delivered through feature updates several times a year. This new development model was branded "Windows as a Service." And after some initial fumbling, Microsoft settled on a cadence of two feature updates a year; one in April, one in October.