From: craekz <firstname.lastname@example.org>
Subject: Re: [9front] [PATCH] patch(1): remove dead link
Date: Fri, 4 Feb 2022 19:11:15 +0100 [thread overview]
Message-ID: <Yf1sOOEcvnA2FfIX@morphine> (raw)
On Wed, Feb 02, 2022 at 12:46:27PM -0500, email@example.com wrote:
> Quoth craekz <firstname.lastname@example.org>:
> > It seems like this link is dead and shouldn't be mentioned anymore.
> > ---
> > diff --git a/sys/man/1/patch b/sys/man/1/patch
> > index 3fb4a490c..badb9298c 100644
> > --- a/sys/man/1/patch
> > +++ b/sys/man/1/patch
> > @@ -154,5 +154,3 @@ file.
> > .B /rc/bin/patch
> > .SH SEE ALSO
> > .IR diff (1)
> > -.br
> > -.B http://plan9.bell-labs.com/wiki/plan9/How_to_contribute
> How about we drop the whole thing instead, since
> that's not how you submit patches to 9front?
If it's just legacy, sure. I think there aren't much people using this
thing or even know about it.
> it also makes room for (eventually) a native,
> simplified version of ape/patch, which can
> live in /bin/patch.
Which would be great!
next prev parent reply other threads:[~2022-02-04 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 16:42 craekz
2022-02-02 17:46 ` ori
2022-02-04 18:11 ` craekz [this message]
2022-02-15 21:34 ` craekz
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).