Re:Introducing Git protocol version 2
by fiatjaf on Friday May 18, 2018 @05:26PM
(#17105081)
That may seen odd, but it could happen in a open-source world: multiple parties releasing different versions of the same piece of software and calling it the same.
[ Parent
| on HN ]
One fun example of this is the so-called RPM "5" fork[0], which is basically dead and almost entirely unused[1].
The result is the main RPM everyone uses will probably stay at version 4.x forever.
[0]: http://rpm5.org/
They could skip a version like PHP did. Among other reasons, since books and articles about PHP 6 had already been written long before PHP 5+1 came out, they went with 7.
Sure, they could. I don't think they've felt the need to. RPM tends to change slowly and conservatively.
Both Git and Linux are trademarked, presumably to prevent such hijinx
Linux is trademarked because of some "hijinx"...
"Initially, nobody registered it, but on August 15, 1994, [...] filed for the trademark Linux, and then demanded royalties from Linux distributors. In 1996, Torvalds and some affected organizations sued him to have the trademark assigned to Torvalds, and, in 1997, the case was settled." https://en.wikipedia.org/wiki/Linux#Copyright,_trademark_and...
Re:Introducing Git protocol version 2
by AdmiralAsshat on Friday May 18, 2018 @05:42PM
(#17105197)
Isn't it customary to at least rename the fork?
Customary, but unless the name is trademarked, not required.