DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 58AMWRD9156553 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 58AMWRD9156553 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=bGKcJNhe X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C5143858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1757543545; bh=DF5f/gw1daz/Km+Ilaredf2mR8TuM6gD6UzgLx0gLWc=; 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=bGKcJNhe7FZOqsXqK8bRvoZVVbQ8IIyFecHOLt2EzCrx3ZHg/8KHSMW/XHaI71kEQ bWVQC25LpH/PtjuVL/C86MzeUTGvh1nFDLo0wWQ/C6Ui7mBaq1N6RVhkS6HjmE2Saz xqm3ldzq6IdyPYq5D2Oc/JXycRHZiMnjJAOy0plU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4FF383858401 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 4FF383858401 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1757543390; cv=none; b=JYwo0j7nEyH478LgrKMnupVFRWcHduXQzKIeCFS8PEKLEcg8N4qCiNwUVTGn45Dg7RIzKEZqSJAxsyzKAZxrjs/hfRJvGkad9Z/EySIc8mWF8euklbzlH1sEbexGBCjZua3Kw7c5G5NuG8hTlU9U47Ivvy72bpVcwABd6pLgvTw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1757543390; c=relaxed/simple; bh=cUS9WRG/hc42wbkM8FEBiQYKWkWLZkb0+bpBbdjbmPE=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=tu663j/cwL2+1Zfyo6uNv/c8HgNU+xfhdc+xVW2E85uW/x0ixgf0s+TbtGFebmykh0Y++vwFdPrLvBaP8Wz//+Xaaw4ritOLQR6IZEIBAdQOHh9OrltCZDV7ScIwRux5huJ/UtdyvuEwwbePIrerUP8dw/j5uZLZT1PG+nar9c8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4FF383858401 Message-ID: <8e90d08e-ae04-4b63-a948-08e142d1204f@SystematicSW.ab.ca> Date: Wed, 10 Sep 2025 16:29:42 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: EOL of (usable) git, switch to Mercurial? Content-Language: en-CA To: cygwin AT cygwin DOT com References: <87bjnjvbbn DOT fsf AT Gerda DOT invalid> Organization: Systematic Software In-Reply-To: <87bjnjvbbn.fsf@Gerda.invalid> X-Stat-Signature: w4gocqkcz7r1gtaerdjamx5ew9gnd3eh X-Rspamd-Server: rspamout08 X-Rspamd-Queue-Id: 7748B20024 X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX19uIt6nEHaC+AiViUrv5fPvnB6Iy3yJoko= X-HE-Tag: 1757543383-588122 X-HE-Meta: U2FsdGVkX1/NMqc58CH8gBpzdhUHssEhAjlL4l0hph0rx5/5Lki4TZLd2l7UVbut12W8B0L4NoyUciQqWruoUbaGJsLWvHjsdj5kHcYMEY1cqCuOGvCLYUJaZhN7PfI31OrCrflYsc6KGkgMBFz0330gExr9QMoA6FjyArwf0UfrBDuSOStCNugBvVRFBNTjWbjBFWUgeGKUrE9/NCkep/NA6rbtkmcSBairMG9h2qE8aYahH+PzVij0BDrNqMcNQaGfJBvhRlAnvySkI1zsc8qv8AfnjfZnAcE7ACMAelmx7HRFkBfZuIQjit5vuvqeYIF3CcabRWYd2kecv867zUb8yVn6UxUXYnEhwK5mqWMO9t520knhMQ== 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 58AMWRD9156553 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. -- 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