Re: Git haas gone wild (Rust), freebsd-update
- In reply to: Poul-Henning Kamp: "Re: Git haas gone wild (Rust), freebsd-update"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 09 Sep 2025 20:26:22 UTC
On Tue, 09 Sep 2025 19:01:27 +0000 "Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > -------- > 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 ? Fossil, despite of "history is forever, no rebase and rewrite" philosophy (e.g. commit amend is made by issuing new control artifact changing properties of chosen) has "artifact shunning" exactly for those "lawyer" situations. -- WBR, @nuclight