DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 58AMf94B159853
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 58AMf94B159853
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=TzhciQf/
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B95F53858C41
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1757544068;
	bh=+WUqUfFbNIB5tR78qZq/wIUH07fZlkuQoAo2GZ9Xgvo=;
	h=To:Cc:References:In-Reply-To:Subject:Date:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=TzhciQf/fH5KDuGP8o1Ew6vupFlvrjpQE98H5VOHt6edKkClKIB9GZpRLGVsj3ljJ
	 0eWT1/OP3B0vaV8ANFZMvGq75ZfN02YT9xeIx1B8LVRprSxWxYcfrKwGZDF0oVA/lp
	 M0pWKYxi8xdgsbT/Nmd2X2li7CytsE2xgiCa8vTw=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8F9163858D35
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8F9163858D35
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1757544001; cv=none;
 b=sg4/NE4vDEDwXmY8lV7XdTvOUWAk1QTgu2MGbaYwBHtNzevvnnp2lN+6XFABgZhpdbb13aD/rW3m7SS2TRWeaASV5in5tNY6U9DJH6tDyYNg4Fjmm9DAAcD5NJEqkZqr4872LPI7dbO22PSX6XUqV6JtzcdIY9+zpGnInMhJRIc=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1757544001; c=relaxed/simple;
 bh=4f/tOYFxtAJdgDWpkkMKj1T4dFJ0XKw3yyOGZnbOR10=;
 h=From:To:Subject:Date:Message-ID:MIME-Version;
 b=rGKjVpLPoWdGOxgAmlUUeUqvx16eD/lkocuS5QQMaAbRIDSOtJ05L7ac5cvC2K5meOM09dzDKFK7UD4XB4c98zysBfd4wp01zD8xddktmB1tv77XuhGmVI//4hJHwTDwzIuu1Xzp/0Lh1kg4UKgc4UdGvWxBHaEiI0O9Bsk4ZVI=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9163858D35
X-Virus-Scanned: Debian amavisd-new at secure.elehost.com
To: <cygwin AT cygwin DOT com>
Cc: "'Brian Inglis'" <Brian DOT Inglis AT SystematicSW DOT ab DOT ca>
References: <CAN0SSYwz6G7-s0w1gWHOf2L-+FsM4362TzvhFxd6LUKEEXRdKg AT mail DOT gmail DOT com>
 <nvc0ckheredqrt1oda607ktpjeurl0o860 AT 4ax DOT com> <87bjnjvbbn DOT fsf AT Gerda DOT invalid>
 <8e90d08e-ae04-4b63-a948-08e142d1204f AT SystematicSW DOT ab DOT ca>
In-Reply-To: <8e90d08e-ae04-4b63-a948-08e142d1204f@SystematicSW.ab.ca>
Subject: RE: EOL of (usable) git, switch to Mercurial?
Date: Wed, 10 Sep 2025 18:39:55 -0400
Organization: Nexbridge Inc.
Message-ID: <060201dc22a3$d8023830$8806a890$@nexbridge.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-ca
Thread-Index: AQG+Erw7V7tZSAa/rDdjUMmt0QtXDAIThAHMAXXwjA0BK39n7bSjejqw
X-Antivirus: Norton (VPS 250910-4, 9/10/2025), Outbound message
X-Antivirus-Status: Clean
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: "Randall S. Becker via Cygwin" <cygwin AT cygwin DOT com>
Reply-To: rsbecker AT nexbridge DOT com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

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.

-Randall


-- 
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