DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 58BJnpfd679489
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 540E13858D26
MIME-Version: 1.0
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>
 <060201dc22a3$d8023830$8806a890$@nexbridge.com>
 <eedf1c38-3309-41ca-afb8-e13015c272ac AT SystematicSW DOT ab DOT ca>
In-Reply-To: <eedf1c38-3309-41ca-afb8-e13015c272ac@SystematicSW.ab.ca>
Date: Thu, 11 Sep 2025 12:48:28 -0700
Message-ID: <CAKFuvzYuLR0HaMyVcBPqP=vC=e1dRa=KhVcup9ndHNUciXB6Bw@mail.gmail.com>
Subject: Re: EOL of (usable) git, switch to Mercurial?
To: cygwin AT cygwin DOT com
Cc: Brian Inglis <Brian DOT Inglis AT systematicsw DOT ab DOT ca>
From: Eric J Korpela via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Eric J Korpela <korpela AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

It used to be a truism that a programmer could write FORTRAN code in any
language.
Now it appears that they are trying to write Python code in every language.

On Thu, Sep 11, 2025 at 11:14 AM Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
wrote:

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

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