Re: Git haas gone wild (Rust), freebsd-update
- Reply: Vadim Goncharov : "Re: Git haas gone wild (Rust), freebsd-update"
- Reply: Norman Gray : "Re: Git haas gone wild (Rust), freebsd-update"
- Reply: Josef 'Jeff' Sipek : "Re: Git haas gone wild (Rust), freebsd-update"
- In reply to: Josef 'Jeff' Sipek : "Re: Git haas gone wild (Rust), freebsd-update"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 09 Sep 2025 19:01:27 UTC
-------- Josef 'Jeff' Sipek writes: > > > > Or switch to Mercurial, https://www.mercurial-scm.org/ and declare git > > > > as obsolete > > > > > > I think that's an excellent idea, for both technical and social reasons! I seem to remember that we had a huge VCS shootout back in previous times and that hg basically lost because they had no way to truly "obliterate" a commit, if for instance laywers waved a credible cease&desist letter. As I recall that (hard!) requirement was caused by the Tetris trademark thing. Is this still a concern for the project ? How does the various VCS's handle that, or have we decided on roll-back-and-recommit as mitigation ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.