From: ori@eigenstate.org
To: 9front@9front.org
Subject: [9front] deleting ape/diff3, ape/diff, and ape/patch?
Date: Sat, 20 Jan 2024 22:16:38 -0500 [thread overview]
Message-ID: <83D5720B7674D9BDA3CFE64D9CB77A88@eigenstate.org> (raw)
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?
next reply other threads:[~2024-01-21 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 3:16 ori [this message]
2024-01-22 12:00 ` ori
2024-01-22 15:02 ` Jacob Moody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83D5720B7674D9BDA3CFE64D9CB77A88@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).