From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch: import replacement for ape/patch
Date: Sun, 22 May 2022 22:18:20 -0500 [thread overview]
Message-ID: <20220522221820.4294230d@spruce.localdomain> (raw)
In-Reply-To: <5BED10E2E8586FE65164516C75BFE8CC@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Sun, 22 May 2022 19:09:40 -0400
ori@eigenstate.org wrote:
> We've been dragging along an antique version of Gnu patch
> as part of ape. It's a bulky program with built in remote
> code execution as part of ed-style diffs.
This will conflict with /rc/bin/patch and /sys/man/1/patch,
which I'm all for removing.
Attached is my edit of the man page:
correct Synopsis patch italics
clarify what patch does
Addtions -> Additions
fix table italics
clarify -p
in See Also, add comma
in Bugs, use all bold for commands
I can't seem to apply your diff with your program:
cpu% touch patch patch.c
cpu% lc
6.out* diff patch patch.c
cpu% 6.out diff
6.out: diff:4: unable to find patch offset
cpu% 6.out -p4 diff
6.out: open null: 'null' not found
cpu% ape/patch -i diff
patching file `patch'
patching file `patch.c'
cpu%
I'm guessing /dev/null is special-cased in gnu patch.
Thanks,
Amavect
[-- Attachment #2: patch.man --]
[-- Type: application/x-troff-man, Size: 967 bytes --]
next prev parent reply other threads:[~2022-05-23 3:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 22:57 ori
2022-05-22 23:09 ` ori
2022-05-23 3:18 ` Amavect [this message]
2022-05-23 12:57 ` Humm
2022-05-24 2:38 ` Amavect
2022-05-24 16:39 ` Humm
2022-05-24 18:44 ` umbraticus
2022-05-24 19:42 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-24 21:19 ` Amavect
2022-05-23 21:40 ` ori
2022-05-23 23:51 ` ori
2022-05-28 21:09 ` ori
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=20220522221820.4294230d@spruce.localdomain \
--to=amavect@gmail.com \
--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).