From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id 991D723DEA
	for <ml@inbox.vuxu.org>; Sun, 21 Jan 2024 04:18:04 +0100 (CET)
Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Sat Jan 20 22:16:59 -0500 2024
Received: from mimir.eigenstate.org (localhost [127.0.0.1])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTP id f6523449
	for <9front@9front.org>;
	Sat, 20 Jan 2024 19:16:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eigenstate.org; h=
	message-id:to:subject:date:from:mime-version:content-type
	:content-transfer-encoding; s=mail; bh=muU4xWC/VQ6yOMMUmx4R3h84w
	D8=; b=gWDHGRMLrr+Qb2LZtaw5k+CBGvvXxxYRRL+xPSKi8xEEkYcPir3VNd+k8
	2Ssv9B97/UN9FFWaIQh2iwNWh/WBIgXjpXCHiJ/8owXopakDjordExT2dfgT4k9q
	8cAJtFvdJbzqLmYU8IyROrMqgfAk9ZACzWTRB9jo2YRa0jdSms=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=message-id
	:to:subject:date:from:mime-version:content-type
	:content-transfer-encoding; q=dns; s=mail; b=gDr9kaXztKzr8cCv+Ji
	KXNuKKgnVs0yMsYg16GfE5AIgpSoW29m6OUHUM/6S1dkYMFKkCgIW0mEcKVKj2zi
	X/ObhgYUxmrBm0xc7q2FecAqROg5d9Ww0Ym86EnDp7XLw6uVRTSO9E5mUSPlkBXm
	sJ/NwcCej/Tced5+2/QDmiNY=
Received: from stockyard (<unknown> [205.220.129.241])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id bdf07f54 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Sat, 20 Jan 2024 19:16:54 -0800 (PST)
Message-ID: <83D5720B7674D9BDA3CFE64D9CB77A88@eigenstate.org>
To: 9front@9front.org
Date: Sat, 20 Jan 2024 22:16:38 -0500
From: ori@eigenstate.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: ORM over YAML deep-learning hosting-based extension-aware layer 
Subject: [9front] deleting ape/diff3, ape/diff, and ape/patch?
Reply-To: 9front@9front.org
Precedence: bulk

As of the last commit to cmd/diff/merge3, we should have
a usable native 3-way merge in tree. Barring bugs, it
should be able to do all that our in-tree scripts need.

As a result, I'd like to remove the buggy, crashy, and
obsolte ape/patch, ape/diff, and ape/diff3 utilities
from our tree by default, and move it into an extrenal
repository, where it will be just as well maintaned as
it was in-tree.

Are there any people currently using them in scripts?
Are there any missing features that would prevent a
transition of them to the native tools?

We will be losing the ability to apply non-unified
patches.

Are there any other objections?