News for hackers. Stuff that matters.
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @04:37PM (#43756199)
Not good enough. All previous commits still infringe Spegel's copyright, given they are still available and distributed. I would assume the point release also infringes copyright.

You are Microsoft. You can do better.

Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @06:32PM (#43757237)
Very silly, they can't rewrite the commit history nor would it be proper to update old packaged releases.
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @06:35PM (#43757268)
What do you mean they can't rewrite the commits? They can, they should, and it's really easy to do so. As for the packages, they should be taken offline.
Re:Getting Forked by Microsoft by wilg on Monday April 21, 2025 @08:02PM (#43757773)
They should neither rewrite the commits nor take the old packages offline. It's not worth a huge potential clusterfuck when the issue has been fixed on the latest version.
Re:Getting Forked by Microsoft by kassner on Monday April 21, 2025 @08:33PM (#43757967)
They should absolutely do it. They made a serious mistake and should pay for it, even if that means every Microsoft developer having to rebase all their WIP branches. The more expensive it gets the more they’ll pay attention to those things in the future.
Re:Getting Forked by Microsoft by saagarjha on Monday April 21, 2025 @11:40PM (#43758893)
Why not just fire the entire division? Maybe they should shut down the company?
Re:Getting Forked by Microsoft by vvillena on Monday April 21, 2025 @08:49PM (#43758078)
You might be overestimating how hard this is, because it's not hard at all. It takes less than half an hour to create a script that does it.
Re:Getting Forked by Microsoft by Mashimo on Tuesday April 22, 2025 @04:39AM (#43760168)
What is the benefit of re-writing the git history?
Re:Getting Forked by Microsoft by guappa on Tuesday April 22, 2025 @06:30AM (#43760653)
Complying with the terms of use instead of infringing copyright
Re:Getting Forked by Microsoft by wilg on Tuesday April 22, 2025 @05:25PM (#43766462)
The terms of the license don’t require you to modify the git history that’s a goofy interpretation.
Re:Getting Forked by Microsoft by guappa on Wednesday April 23, 2025 @04:26AM (#43769822)
The terms of the license require you to ship the copyright note. Their latest release is in violation…
Re:Getting Forked by Microsoft by miffy900 on Tuesday April 22, 2025 @12:36AM (#43759108)
Rewriting those commits would effectively allow them to erase their mistake, which kind of lets Microsoft off the hook in a way.
Re:Getting Forked by Microsoft by hoseja on Tuesday April 22, 2025 @06:11AM (#43760568)
Git isn't some kind of secure blockchain.