From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ipso(1) patch
Date: Sun, 14 Mar 2004 19:25:25 +0400 [thread overview]
Message-ID: <200403141525.i2EFPPo1068962@adat.davidashen.net> (raw)
In-Reply-To: <2004031413541300-84310@Symmetry.UUCP>
> BTW, is there any common format for supplying patches for Plan 9?
> I guess that using diff(1) would cause trouble when patching an
> already-patched file, since it uses absolute line numbers.
>
> Below, there is a context diff containing my changes to ipso, in
> case anyone is interested.
It has been recently discussed on the list, with the usual (for 9fans)
friendliness and clarity of instructions.
A way that works is to use ape/patch -- so your context diff is OK.
ape/patch is Gnu patch 2.5.0.
The right way is to use patch(1), except that it does not work.
You must bind your /tmp (or another) directory before
/n/sources/patch because /n/sources/patch is not writable, then
roll the arcive created by patch and deliver it somehow to 'Plan
9 developers'. I wonder what the 'Plan 9 developers' use to
merge patches in, if they do that at all, since many patches
generated with diff are just posted to the list.
I think that a good solution that does not have 'gnu' in its name
is not yet available for Plan 9.
next prev parent reply other threads:[~2004-03-14 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 13:54 Nils M Holm
2004-03-14 15:25 ` David Tolpin [this message]
2004-03-14 15:36 ` David Presotto
2004-03-14 18:55 ` boyd, rounin
2004-03-14 18:54 ` boyd, rounin
2004-03-14 16:07 ` David Presotto
2004-03-15 7:29 ` Nils M Holm
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=200403141525.i2EFPPo1068962@adat.davidashen.net \
--to=dvd@davidashen.net \
--cc=9fans@cse.psu.edu \
/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).