DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 58BIEl8K643485 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 58BIEl8K643485 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=MVJAdCeH X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 43D513858406 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1757614485; bh=2jDYZCy1tiRqtYyYyQxIH7YlV47+y5W9BZuA73oxzyA=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=MVJAdCeHTqX7k653nhKLdX8mVStcZlkgnPsFVTmNK+NqLy1tmWGoDLQZDeGQkHaN5 WuRRRCBsYlisr/ZCsvCdgDhy5DHDNeClP+hzJBOZth1riI71SDYCzPKm0/tC2NVrcd fizZbctYEim15nieDvQG7vvVeaq8IYUozSijQvxI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 688BE3858D26 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 688BE3858D26 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1757614426; cv=none; b=EdT0KwXiZ5trszRxgK9/o5bbAlk2GkNAmLcfwZtc1zDaleJl5NUQYTwqYO2Bdpx4iq22gITK0R/V1xemuuzrVY8sNoqaGMm0Lm5XeHVIJW0EKfYB/cnMxjZnOQrNFgERIGQQCHRK/ZhW4wKYpupS8mrSSgBjFxISl59XBw4y6MM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1757614426; c=relaxed/simple; bh=rStKW3A9coV52bmw8fYb5RcodHfYU+6V15g7VKo8MHA=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=Qd1nKD4fXVbJhScIRcK6wASogwEcdeLfm4uhJWVdditA8toPf4swXkrX0MdTYduJoOzolTZVSOCEiYrLqcwqy5WaOTOfsflD2H5B0eT/n23kl2UdcfmxvMaJ0aPUe18ccJ3KGAvusO3O1xnFNw1jGU0udLDYoILdx3p/5mzj0S0= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 688BE3858D26 Message-ID: Date: Thu, 11 Sep 2025 12:13:43 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: EOL of (usable) git, switch to Mercurial? To: cygwin AT cygwin DOT com References: <87bjnjvbbn DOT fsf AT Gerda DOT invalid> <8e90d08e-ae04-4b63-a948-08e142d1204f AT SystematicSW DOT ab DOT ca> <060201dc22a3$d8023830$8806a890$@nexbridge.com> Content-Language: en-CA Organization: Systematic Software In-Reply-To: <060201dc22a3$d8023830$8806a890$@nexbridge.com> X-Stat-Signature: abk6xdj3nhgfxqiytzgzed49gs3cn5de X-Rspamd-Server: rspamout07 X-Rspamd-Queue-Id: 721B917 X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX18g3KMLq8WbofDCqQUNLW3pLHHAwunLGWw= X-HE-Tag: 1757614424-839989 X-HE-Meta: U2FsdGVkX1+168zCByIWUsyu0dXKr0QmPzqhLCHPJHZzX/DSo12RGwrHGTqyn7r1YkEjuV4pIneiom1qRVgOT2tUI9Yb1SpcoQWq1zO49lmXM07yYdOJF4zrUY/6dxkSXeHzz5GkgiyPl30bO2sWo+lI/OOzt+CJMUPde9gfG5ijZ9TB0NxYE3aJnRKOn8EZxMdc05aqieEkMOSkFdwj0bX40QFtCz2RztgYfNQ1FhDn6nzBL1WIY8BYDMPg8Cbn/sf+dKdc12zXVSR7UbEhnlSDfCo6GAeJzs/8rSyT2RNNgZiSwa7dwXOrsXF3P7xUVL2fZ09Kj71VnaDqNfjHNMwZEzppEQ7TJqVGd59OrN2GhJ1++xmUrRnQqB9xk/eLJaWAhVU4DVw= X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 58BIEl8K643485 On 2025-09-10 16:39, Randall S. Becker via Cygwin wrote: > On September 10, 2025 6:30 PM, Brian Inglis wrote: >> On 2025-09-09 10:29, ASSI via Cygwin wrote: >>> Andrew Schulman via Cygwin writes: >>>> On Tue, 9 Sep 2025 10:23:13 +0200, Mark Liam Brown via Cygwin wrote: >>>>> Since git has decided to EOL itself by a switch to RUST (which poses >>>>> a chicken and egg problem for bootstrapping, among other technical, >>>>> political and licensing issues), >> >> What appear to be the remaining licensing and political issues? >> >>>> For those of us who aren't in the know, could you please provide some >>>> links to git's plans and what the issues are? A search on "git rust" >>>> turns up a lot of stuff but it's hard to know what's relevant. >> >>> TL;DR: This did not happen (not yet anyway) and it won't happen in the >>> near future either. >>> https://lore.kernel.org/all/20250904-b4-pks-rust-breaking-change-v1-0- >>> 3af1d25e0be9 AT pks DOT im/ >> I consider 2026H2 - a year - pretty near, with possibly another year and a half of >> security patches, giving us 1-2.5 years, realistically 1.5 years to decide whether we >> could get rust working, or should migrate to a git successor. > > Unfortunately for the rest of us non-Rust people, successors appear to be written > In Rust also. This does not make me feel good about the future of DVCS systems. Especially when people seem to be reinventing the wheel rewriting existing code in this decade's systems programming language: https://en.wikipedia.org/wiki/Category:Systems_programming_languages -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple