Date: Tue, 9 Sep 2025 13:13:46 +0300 From: Vadim Goncharov <vadimnuclight@gmail.com> To: Norman Gray <gray@nxg.name> Cc: Mark Liam Brown <brownmarkliam@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: Git haas gone wild (Rust), freebsd-update Message-ID: <20250909131346.1e1011ea@nuclight.lan> In-Reply-To: <39D21672-603B-42A6-8820-F274FCC1191D@nxg.name> References: <00202803-6a1a-44ca-b110-9f1404d2c9bc@FreeBSD.org> <CAN0SSYwGC1G8s5Ygb6rKqX2yPSoCCeJAyFk0gscBW0b94BwWRA@mail.gmail.com> <39D21672-603B-42A6-8820-F274FCC1191D@nxg.name>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 09 Sep 2025 09:39:20 +0100 Norman Gray <gray@nxg.name> wrote: > Mark, hello. > > On 9 Sep 2025, at 9:18, Mark Liam Brown wrote: > > > 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! > > (It's worth noting, though, that the Mercurial developers have, for the > past couple of years, been incrementally and _very_ carefully replacing > performance-critical Python components with Rust equivalents > <https://www.mercurial-scm.org/help/topics/rust>. The words > ‘incremental’ and ‘careful’ are pretty much hallmarks of > Mercurial's development history.) So again, no actual alternative except Fossil ? :-)* Which is in C and could be statically compiled to single binary. *as NetBSD experience shows, it will require some interaction and fixes from it's developers (same people as SQLite team, good old techies) from performance side and some missing git features. However, if not (and likely not, as freebsd.org decision-makers do not like innovations), Fossil, due to it's "static" possibility, still could be considered for *binary* files storage - that is, replacement for freebsd-update(8). -- WBR, @nuclight
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250909131346.1e1011ea>