From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch: import replacement for ape/patch
Date: Tue, 24 May 2022 16:19:10 -0500 [thread overview]
Message-ID: <20220524161910.777210fb@spruce.localdomain> (raw)
In-Reply-To: <Yo0KQHx7DkDy+pT+@beryllium.local>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On Tue, 24 May 2022 16:39:28 +0000
Humm <hummsmith42@gmail.com> wrote:
> Quoting RFC4263:
Neat, but I have no clue how to configure process= in claws mail.
Since application/x-troff-man is nonstandard,
I'll just default it to text/troff and call it a day.
> While much documentation for specific troffs indeed says that blank
> lines have the same effect as `.sp 1`—they do implement that, after
> all—that behavior is not ubiquitous. A warning is given, for
> example, by mandoc. Quoting mandoc(1):
There's disagreement from others, but we can all agree that .PP is the
correct choice for new paragraphs.
It has slightly shorter spacing than a blank line in page.
Attached is the final revision for ori's patch man page.
Thanks,
Amavect
[-- Attachment #2.1: Type: text/plain, Size: 306 bytes --]
from postmaster@9front:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/troff
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=patch.man
[-- Attachment #2.2: patch.man.suspect --]
[-- Type: application/octet-stream, Size: 1027 bytes --]
.TH PATCH 1
.SH NAME
patch \- apply diffs
.SH SYNOPSIS
.B patch
[
.B -R
]
[
.B -p
.I nstrip
]
[
.B -f
.I maxfuzz
]
[
.I patch ...
]
.SH DESCRIPTION
.I Patch
takes a patch file in unified diff format and applies the differences to the file tree.
If the file is not an exact match, it will search forwards and
backwards for the surrounding context up to
.I maxfuzz
lines.
.PP
The following options are supported:
.TP
.B -R
Reverse direction of the patch. Additions become removals,
and the new and old file names are swapped.
.TP
.BI -p \ nstrip
Remove the prefix containing
.I nstrip
leading slashes from each file path in the diff file.
.TP
.BI -f \ maxfuzz
Controls how far
.I patch
searches for context when applying a patch.
If not specified, this defaults to 250 lines.
.SH SEE ALSO
.IR diff (1),
.IR git/export (1)
.SH BUGS
.PP
The output of
.B diff -c
is not handled.
.PP
Reject files and backups are not supported.
.PP
All files are processed in memory, which limits
the files handled to 2 gigabytes on 32-bit systems.
next prev parent reply other threads:[~2022-05-24 21:23 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
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 [this message]
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=20220524161910.777210fb@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).